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

show_diff has been deprecated #132

Open
herisanu opened this issue Oct 2, 2016 · 8 comments
Open

show_diff has been deprecated #132

herisanu opened this issue Oct 2, 2016 · 8 comments

Comments

@herisanu
Copy link

herisanu commented Oct 2, 2016

Let's change show_diff into show_changes: False

[WARNING ] /usr/lib/python2.7/site-packages/salt/states/file.py:1655: DeprecationWarning: The 'show_diff' argument to the file.managed state has been deprecated, please use 'show_changes' instead.

How to re-create: run formula on latest saltstack.
Link to code: https://github.com/saltstack-formulas/users-formula/blob/master/users/init.sls#L180

Would you be ok with this change?

@blbradley
Copy link

I see show_diff in the 2016.3.3 docs. So, I don't think this is a good idea yet.

Also, backwards compatibility will need to be maintained for a long period of time.

@herisanu
Copy link
Author

herisanu commented Oct 2, 2016

Yeah, backwards compatibility will be an issue. Would you consider using jinja for this?
Something along the lines of:

{{ users.show_diff }}: False

Where show_diff is set in defaults.yaml or map.jinja (with a grains filter on saltversion maybe)
This will give me the option of throwing this in a pillar.

@blbradley
Copy link

I would use a conditional that checks the salt version and uses the appropriate parameter. No pillar config required.

@herisanu
Copy link
Author

herisanu commented Oct 2, 2016

Yeah, right. Or that. Is it cool to send a PR with this?

@blbradley
Copy link

blbradley commented Oct 2, 2016

I believe you should wait until there is a stable version of Salt that shows up in the docs with show_changes.

But don't mind me. I don't actually use this formula. Edit: yet.

@noelmcloughlin
Copy link
Member

@herisanu Now is good time to do this. thx

@herisanu
Copy link
Author

Heh an issue from 2016 :). Let me re-read the formula and create a PR then.

@noelmcloughlin
Copy link
Member

noelmcloughlin commented Jun 12, 2019

Chuckle, our past comes back to haunt us sometimes

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

No branches or pull requests

3 participants