-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate valid fernet keys for local deployment #196
Comments
kashyapkannan
pushed a commit
to kashyapkannan/amazon-mwaa-docker-images
that referenced
this issue
Jan 3, 2025
kashyapkannan
pushed a commit
to kashyapkannan/amazon-mwaa-docker-images
that referenced
this issue
Jan 3, 2025
kashyapkannan
pushed a commit
to kashyapkannan/amazon-mwaa-docker-images
that referenced
this issue
Jan 7, 2025
kashyapkannan
pushed a commit
to kashyapkannan/amazon-mwaa-docker-images
that referenced
this issue
Jan 7, 2025
vishalvijay18
pushed a commit
that referenced
this issue
Jan 8, 2025
#207) *Issue #, if available:* #196 *Description of changes:* - Modified run.sh to generate, cache and pass valid fernet key to the docker-compose file. - Added a script to be able to use pip install in run.sh to temporarily install dependencies needed before the bootstrap steps, like in this use-case. - Updated pip_install_check.py and run_all.py quality_check files' shebang for better portability. - Updated lint_bash check to exclude .venv's generated scripts. *Description of testing:* - Built and ran image locally with the run.sh script. - Used log statements to verify the fernet key was valid and being passed correctly. By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice. Co-authored-by: Kashyap Kannan <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
The current fernet key in docker-compose file is deliberately invalid. This prevents the use of any feature relying on fernet encryption for local deployments.
To prevent hard-coding a valid fernet key (which risks general public using it in production), we should update run.sh to generate a valid fernet key, cache it locally, and pass it as an environment variable to the docker-compose file. So when run.sh is executed it either gets key from the cache, or if it doesn't exist, it generates a new one.
The text was updated successfully, but these errors were encountered: