-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[WIP][2019.2] Pillar refresh fixes #52377
[WIP][2019.2] Pillar refresh fixes #52377
Conversation
…ddition to self.opts['pillar'].
…t into pillar_refresh_fixes
@garethgreenaway it's not finished yet. Am I right? |
@DmitryKuzmenko just not sure if my approach is 100% correct. |
I don't see how it could help. Is the |
@DmitryKuzmenko |
@garethgreenaway ping! Does this PR make any sense now? |
@garethgreenaway want to rebase this against |
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.
No point in reviewing until the changes are against the master branch
Redo changes against the master branch
I wonder if this still needed |
@garethgreenaway is this still needed or can it be closed? |
@Ch3LL Looks like another PR fixed the issue. Closing. |
What does this PR do?
Updates
__pillar__
in addition to self.opts['pillar'] when a state run happens.What issues does this PR fix or reference?
#52354
Previous Behavior
During a state run if a pillar error occurred it would be preserved in
__pillar__
, so on subsequent state runs during the error checking the run would be flagged as having an error even if the issue has been corrected.New Behavior
When self.opts['pillar'] is updated, update
__pillar__
as well.Tests written?
No
Commits signed with GPG?
Yes
Please review Salt's Contributing Guide for best practices.
See GitHub's page on GPG signing for more information about signing commits with GPG.