You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proposed title of this feature request?
Tagging VMware Networks
What is the nature and description of the request?
The user is looking for a way to mask some VMware networks from users. They already have this configured on the VMware side using RBAC but this does not pass over to CloudForms. There is a similar RFE but it discusses removing the add networks option when reconfiguring a VM, this user needs the option to change/add networks just not provide visibility to all available networks in VMware.
Why does the user need this?
Currently, users are able to select networks that should be unavailable to them which leads to provisioning failures because VMware blocks the request based on its RBAC.
How would the user like to achieve this?
Add Tagging for VMware networks
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions! More information about the ManageIQ triage process can be found in the traige process documentation.
Tagging VMware Networks
The user is looking for a way to mask some VMware networks from users. They already have this configured on the VMware side using RBAC but this does not pass over to CloudForms. There is a similar RFE but it discusses removing the add networks option when reconfiguring a VM, this user needs the option to change/add networks just not provide visibility to all available networks in VMware.
Currently, users are able to select networks that should be unavailable to them which leads to provisioning failures because VMware blocks the request based on its RBAC.
Add Tagging for VMware networks
The text was updated successfully, but these errors were encountered: