-
Notifications
You must be signed in to change notification settings - Fork 346
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
vmware_object_role_permission: Parameter object_name also accepts paths #2315
base: main
Are you sure you want to change the base?
Conversation
Build failed. ❌ ansible-tox-linters FAILURE in 4m 19s |
Build failed. ❌ ansible-tox-linters FAILURE in 4m 26s |
Build failed. ✔️ ansible-tox-linters SUCCESS in 4m 26s |
…re seems to be related to something outside the code
Build succeeded. ✔️ ansible-tox-linters SUCCESS in 4m 27s |
SUMMARY
You can now pass a path as object_name to identify an object where the name is not unique
Fixes #1217
ISSUE TYPE
COMPONENT NAME
vmware_object_role_permission
ADDITIONAL INFORMATION
This is required if you want to use this module for objects where the name is not unique. This happened to me in a folder structure where we first had the environment type (prod/test/dev) and below this structure the service type (web/database etc.).
In this structure we had multiple folders with eg. the name database (/dev/database and /prod/database) and those folders could not be identified by their name.