Skip to content
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

Closed

Conversation

garethgreenaway
Copy link
Contributor

@garethgreenaway garethgreenaway commented Apr 1, 2019

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.

@dwoz dwoz added the v2019.2.1 unsupported version label Apr 11, 2019
@DmitryKuzmenko
Copy link
Contributor

@garethgreenaway it's not finished yet. Am I right?

@garethgreenaway
Copy link
Contributor Author

@DmitryKuzmenko just not sure if my approach is 100% correct.

@DmitryKuzmenko
Copy link
Contributor

I don't see how it could help. Is the salt.state.__pillar__ dunder used anywhere? I don't see local usages in that file.

@garethgreenaway
Copy link
Contributor Author

@DmitryKuzmenko __pillar__ is used in other places but wasn't being updated in this location when salt.opts['pillar'] was being updated.

@DmitryKuzmenko
Copy link
Contributor

@garethgreenaway ping! Does this PR make any sense now?

@sagetherage sagetherage removed the v2019.2.1 unsupported version label May 22, 2020
@sagetherage sagetherage removed the request for review from DmitryKuzmenko November 18, 2020 18:06
@sagetherage sagetherage added the v2019.2x unsupported versions label Nov 18, 2020
@sagetherage
Copy link
Contributor

@garethgreenaway want to rebase this against master branch?

@sagetherage sagetherage removed Reviewers-Assigned v2019.2x unsupported versions labels May 24, 2021
Copy link
Contributor

@dmurphy18 dmurphy18 left a 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

@Oloremo
Copy link
Contributor

Oloremo commented Sep 9, 2021

I wonder if this still needed

@Ch3LL
Copy link
Contributor

Ch3LL commented Nov 3, 2022

@garethgreenaway is this still needed or can it be closed?

@garethgreenaway
Copy link
Contributor Author

@Ch3LL Looks like another PR fixed the issue. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants