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

vmware_object_role_permission: Parameter object_name also accepts paths #2315

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

Fleege
Copy link

@Fleege Fleege commented Feb 13, 2025

SUMMARY

You can now pass a path as object_name to identify an object where the name is not unique

Fixes #1217

ISSUE TYPE
  • Feature Pull Request
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.

…re seems to be related to something outside the code
@Fleege Fleege marked this pull request as ready for review February 13, 2025 11:40
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

Successfully merging this pull request may close these issues.

Unable to use vmware_object_role_permission on multiple VM folders of the same name
1 participant