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
make cached pillars use pillarenv rather than saltenv #43689
Conversation
@The-Loeki, thanks for your PR! By analyzing the history of the files in this pull request, we identified @cachedout, @terminalmage and @thatch45 to be potential reviewers. |
@terminalmage Can you help review this one? |
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.
I've not dealt much with the pillar cache feature, but the default value for pillarenv
is None
. I would assume that this would still work, since None
is a hashable value and thus could occupy a spot in the cache dict. @The-Loeki have you tested this without explicitly defining the pillarenv to make sure it works? I'm particularly interested in the debug logging that will show what the cache dict looks like.
@terminalmage good point! I hadn't considered it, but as you suspect turns out it 'just works':
|
They all use the same dictionary structure, if I understand correctly. @cachedout can you sanity-check me here? |
What does this PR do?
when
pillar_cache
isTrue
, thepillarenv
args stop working.This fixes the problem for me, but I'm unsure about the further ramifications.
What issues does this PR fix or reference?
fixes #42393
which is probably a duplicate of #36153
Previous / New Behavior
I did a search & replace in the affected function
saltenv
>pillarenv