fallback to ext_pillar in pillar match if there is no pillar in __opts__ #55624
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.
What does this PR do?
If there is 'pillar' in
__opts__
the matchers would break. This PR determines if there is a 'pillar' object and uses 'ext_pillar' if there is none.What issues does this PR fix or reference?
#52567
Previous Behavior
Previously the matcher would just call
__opts__['pillar']
.New Behavior
The matcher checks for
__opts__['pillar']
. If there is none, it calls__opts__['ext_pillar']
instead.Tests written?
No
Commits signed with GPG?
No