-
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
Fixes bug in modules/pillar.py #58971
Fixes bug in modules/pillar.py #58971
Conversation
The method obfuscate needs **kwargs in parameters so its able to use items() fully, as intended. This fixes that problem.
Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar. |
@tommygrumheden What is the reason for the change blindly accepting |
Hi @garethgreenaway |
@tommygrumheden Thanks. I see why this is needed and it looks like we include it in other functions in the pillar module. I added a quick test to ensure that kwargs such as saltenv are passed along to |
Congratulations on your first PR being merged! 🎉 |
Thanks for fixing a test! Happy to be contributing :) :) |
What does this PR do?
The method obfuscate needs **kwargs in parameters so its able to use items() fully, as intended.
This fixes that problem.
No tests / changelog / docs supplied in PR.
What issues does this PR fix or reference?
Fixes: No issue created.
Previous Behavior
ERROR executing 'pillar.obfuscate': The following keyword arguments are not valid: saltenv=XXX
New Behavior
saltenv works.
Merge requirements satisfied?
[NOTICE] Bug fixes or features added to Salt require tests.
Commits signed with GPG?
No
Please review Salt's Contributing Guide for best practices.
See GitHub's page on GPG signing for more information about signing commits with GPG.