-
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
Use encoding when caching pillar data #52195
Use encoding when caching pillar data #52195
Conversation
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.
This looks like a unit test with all the mocking
Those are just pieces that are irrelevant to the test. Opportunity to refactor maybe? |
86df0e4
to
d772631
Compare
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.
See my utf-8 comment and the linter.
4f832c9
to
efbc8b7
Compare
@waynew Sorry, I missed this. Just checked - it fixes my issue! |
efbc8b7
to
f99f986
Compare
f99f986
to
0a89cfd
Compare
@dwoz lint issue is fixed, also it turns out there exists an SLS_ENCODING already, so I changed to using that. |
re-run all |
63d2c2f
to
50e8849
Compare
50e8849
to
79fb4de
Compare
Fixes saltstack#51854 and ports saltstack#52195 to master
What does this PR do?
Fixes #51854 - sets the encoding when using the yaml dump
What issues does this PR fix or reference?
#51854
Previous Behavior
Caching just used the default encoding, which broke on Python3 where it expected to be writing bytes out to the file.
New Behavior
Now it specifies the encoding so dump expects the pillar in the form that it is.
Tests written?
Yes
Commits signed with GPG?
Yes