Conversation
Signed-off-by: Tim Paine <3105306+timkpaine@users.noreply.github.com>
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
1 participant
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.
Two unrelated papercuts found while bringing an MWAA environment up on Airflow 3.
Offline DAG generation has no usable metastore, so resolving a
Variablepassword always fails and falls back toUNRESOLVED_PASSWORD. That is expected and already handled, but Airflow logs a full traceback at ERROR for every secrets backend it fails to read before falling through, so every generate run emits a wall of noise.Host.hooknow raises theairflow.models.variablelogger to CRITICAL for the duration of the lookup it already tolerates.The pool manager DAG defaulted to
*/5 * * * *. Centrally configured pools change about as often as the config is deployed, so reconciling every five minutes is mostly wasted scheduler work. Default is now@daily; anything that already pinsdag.scheduleis unaffected, since the validators only backfill fields that were not explicitly set.