[ETL-365] Launch stacks during push and PR to dev AWS account #24
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.
Purpose: This PR follows the same logic as BridgeDownstream in that it launches stacks to the "recover" and feature branch namespaces of the recover develop account.
This PR also parameterizes some of the python and glue versions used in the glue job stacks as we have varying python and glue versions to be used in the highest level stack config:
config/config.yaml
. Was unable to dynamically parameterize the lambda python runtime in the sam template to this stack because findings say it's not possible to pass this through to the lambda sam template.