Binding AWS Kinesis - reuse client credentials #3509
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Should remove the need to define the AWS secret(key, id, session) information in the binding definition and instead use the existing AWS mechanisms of using metadata server, env, config, and other methods.
TODO: update documentation and code to be more obvious on what is going on. Also, will add a few lines about how this will create a DynamoDB table and how it is named.
Issue reference
Implements issue #3508
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: