Closed
Conversation
Contributor
Author
|
The same error occurred when leaving AIRFLOW__API_AUTH__JWT_SECRET blank, so I randomly put in the secret key value. I don't think it's a good way. Is there another good way |
Member
|
This was resolved in #49681 |
Contributor
|
I added the related functionality to the HELM chart (here: #49923), maybe the docs can also be updated. |
Member
Yep. Contrbutions are welcome. And yes, hard-coding the secret is a bad idea. |
2 tasks
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
4 participants
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.
build Docker-compose file, you will get an error to enter ValueError: The value api_auth/jwt_secret must be set!.
To solve this problem, you entered the temporary secret key of AIRFLOW_API_AUTH_JWT_SECRET in the Docker-compose.yml file.
Closes: #49992