allow access to airflow env stg or prod in all containers #1997
Conversation
This file contains 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
|
Tian-2017
deleted the
allow-access-to-airflow-env-(stg-or-prod)-in-secret-manager-in-all-ecs-containers
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
These keywords "stg" and "prod" are stored in the Secrets Manager under
airflow/variables/envto allow access by containers.The ARN of
airflow/variables/envin 'prod' and 'stg' differs because AWS attaches a unique string to each. If there is a better way to manage access to airflow/variables/env, please let me know. ThanksI know we can pass it from the Airflow DAG to the container, but reading it from Secrets Manager seems more straightforward