fix(cron): drop stale env-var override of persisted provider - #19627
Merged
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Salvage of #15769 onto current main.\n\n## Summary\nCron jobs were passing as to , short-circuiting the resolver's own precedence (explicit arg \u2192 persisted config \u2192 env). Long-lived cron daemons inherit env from their launching shell, so a since-changed env var could resurrect an old provider.\n\n## Validation\nManual review; diff scope self-contained.\n\nOriginal PR: #15769