Adding support for passing host system AWS_ prefixed variables into runiac container #51
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.
fix(chore): preventing multiple loops over the same array
feature(AWS_ vars): Adding AWS_ env var support into run container
Proposed changes
Allowing AWS environment variables to be passed to
runiac
run container, as they were previously restricted to only allow prefixed like: TF_VAR_, ARM_, RUNIAC_.Common environment variables, as presented in the
entrypoint.sh
in the AWS hello world starter, demonstrate the need to allow well-known vars to make their way into the container for use.Issues for these changes
Types of changes
Checklist
README.md
,CHANGELOG.md
, etc. - if appropriate)Dependencies and Blockers
I will be making another PR to the AWS hello world repo adding support for the often used AWS_PROFILE env var.
Relevant Links
AWS CLI/SDK Support Environment Variables
Further comments
None