-
Notifications
You must be signed in to change notification settings - Fork 16.5k
Disable use of LogTemplate table by default #61880
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,17 @@ | ||
| Retrieving historical log templates is disabled in Airflow 2.11.1 | ||
|
|
||
| When you change the log template in Airflow 2.11.1, the historical log templates are not retrieved. | ||
| This means that if you have existing logs that were generated using a different log template, | ||
| they will not be accessible using the new log template. | ||
|
|
||
| This change is due to potential security issues that could arise from retrieving historical log templates, | ||
| which allow Dag Authors to execute arbitrary code in webserver when retrieving logs. | ||
| By disabling the retrieval of historical log templates, Airflow 2.11.1 aims to enhance the security of the | ||
| system and prevent potential vulnerabilities in case the potential of executing arbitrary code in webserver | ||
| is important for Airflow deployment. | ||
|
|
||
| Users who need to access historical logs generated with a different log template will need to manually | ||
| update their log files to match the naming of their historical log files with the latest log template | ||
| configured in Airflow configuration, or they can set the "core.use_historical_filename_templates" | ||
| configuration option to True to enable the retrieval of historical log templates, if they are fine with | ||
| the Dag Authors being able to execute arbitrary code in webserver when retrieving logs. |
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this needs to be {{ }}. like this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really - that's a string that is already default - the
{{is only needed when we read it from config and where it is processed first by Jinja template. But yeah - I will double check if this works as expected (also this fallback is not going to be used most likely - it's only in case the code is run before ProvidersManager discovery - because once providers manager processes it, there is a default defined from provider.yaml.