-
Notifications
You must be signed in to change notification settings - Fork 173
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
Add support for setting ACL rules on certificates #548
Conversation
This commit is copying the contents of an older abandoned merge request by user Hakon, with some minor adjustments like removing dead code and implementing some feedback from the original MR. #94
In hindsight, as I am basically copying Hakon's code, it seems right that he should get credit for it
The assertions are almost certainly wrong, but I wanted to commit anyway to not accidentally revert the stuff that does work.
I do see I have some linting errors, but before I fix those, I just want to understand - if the Windows Server tasks are reporting successful, does that mean the integration tests are all actually passing? |
That is correct, the tests are in group 1 and if they are green then the tests have passed :) |
great! funny enough I see what happened now - I'm assuming because the lint failed, the integration tests didn't run, which would make sense. I'll see what I can do to fix the integration tests. Hopefully I can get them runnning locally; I'd like to not abuse whatever Azure plan this is running on (even if it's free - I don't know if Azure gives free credits to FOSS) |
Simply create a file at |
Ahhhh, I figured out I needed that inventory file, but I hadn't realized the host needed to be called |
Actually sorry the host can be called anything, it just needs to be in a group called |
holy moly, that was quite the experience. @jborean93 this should be ready for an actual review whenever you have time On the bright side, the tests actually did catch a bug! There was no idempotency check in the initial PR, so I added that! |
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.
Thanks for working on this and getting the tests running. I've added a few comments here. The overall implementation looks great, just had a few minor concerns/suggestions.
… with NCryptFreeObject
@jborean93 almost everything has been addressed - there is a question mark surrounding |
Thank you very much for working on this and working on the tests. It great to see a very in depth implementation with tests to cover them! |
Thank you very much for this contribution! I've been manually patching our local install for a long time. |
SUMMARY
I'm making this PR that essentially revives #94 to add support to
Cert:\
paths in win_acl. I tried to follow all the unresolved feedback from #94Fixes #150
ISSUE TYPE
COMPONENT NAME
win_acl
ADDITIONAL INFORMATION
There is one huge caveat that I'm fairly certain my test assertions are wrong, but when I try to use
ansible-test
, I'm getting a very unhelpful error (I'll add more details in a comment), so I'm assuming that's going to block this getting merged. I realize this isn't an Ansible help forum, but if you happen to have any suggestions on what part of this stack trace is useful, I'd love to try and get these tests running