-
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
Syndics honor MoM acl #63428
Syndics honor MoM acl #63428
Conversation
a6bb27a
to
43ecda0
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.
Only one problem that I see, and that's in the test suite.
I'm going to check this out and bang on it a bit more. I'm also seeing some failures here: https://github.com/saltstack/salt/actions/runs/3864153908/jobs/6586792092 that are concerning
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.
Okay, I opened a PR against your fork and I've also added I think what would make the docstring 👍 - if you want to finish this up I can close mine in favor of this PR, or vice versa and I can go ahead and combine these changes with my PR.
Those smol changes and this is ready to rock! 🎉
Looks like the test failures are possibly related to this change. |
7090670
to
8ace01d
Compare
We want to ensure that targeting invalid minions does *not* allow us to run any sort of shenanigans on the minions in question! This ensures that valid commands (i.e. file.touch in this case) cannot inadvertently be sent to minions that we don't have ACL for.
ee5ab12
to
9d0ba70
Compare
It's possible that the output of ls is different for some reason, but test -f should always return 0 if the file exists, or 1 otherwise. We want it to be not 0.
What does this PR do?
This is an alternate approach to #63257
What issues does this PR fix or reference?
Fixes:
#62618
#62577
Previous Behavior
Remove this section if not relevant
New Behavior
Remove this section if not relevant
Merge requirements satisfied?
[NOTICE] Bug fixes or features added to Salt require tests.
Commits signed with GPG?
Yes/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.