Code of Conduct
This project has a Code of Conduct that all participants are expected to understand and follow:
Description
The resource nsxt_policy_user_management_role_binding wants to be the single source of truth for a users role binding. This kind of resource is desired in many, if not most cases, but it prevents one from duplicating the functionality of where the portal uses a PUT request to the backend.
The realistic scenario this would solve is where a user only has the VPC admin role, and wants to delegate further permissions to other users. This is doable today with the portal, but fails with this provider due to the nature of the resource using POST rather than PUT.
Describe alternatives you've considered
N/A
References
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Code of Conduct
This project has a Code of Conduct that all participants are expected to understand and follow:
Description
The resource nsxt_policy_user_management_role_binding wants to be the single source of truth for a users role binding. This kind of resource is desired in many, if not most cases, but it prevents one from duplicating the functionality of where the portal uses a PUT request to the backend.
The realistic scenario this would solve is where a user only has the VPC admin role, and wants to delegate further permissions to other users. This is doable today with the portal, but fails with this provider due to the nature of the resource using POST rather than PUT.
Describe alternatives you've considered
N/A
References
Community Note