AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY for S3 access - #14
Open
william-episource wants to merge 3 commits into
Open
AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY for S3 access#14william-episource wants to merge 3 commits into
william-episource wants to merge 3 commits into
Conversation
updated deployment.yaml and values.yaml to accept params access_id and access_secret for AWS S3
updated deployment.yaml to use more generic approach to filling out key-value pairs for S3 and other services
Author
|
@larribas I made a revision to accommodate S3 credentials |
revised key names
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
updated deployment.yaml and values.yaml to accept params access_id and access_secret for AWS S3