-
Notifications
You must be signed in to change notification settings - Fork 458
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
vsphere_entity_permissions
- global permissions preventing removing root folder permissions
#1400
Comments
Adding to this, I think the permissions are removed on non-root folders as well. |
This has been a pain point for us, too. |
An update based on my expereince with this issue. Terraform Version
vSphere Provider Version:
Affected Resource(s)
Terraform Configuration Files
When applying the plan I see that 2 permissions will change....
However, when applied, it completes but with an erroneous error for another role and permission....
The results are corrects and the users are set to the "No access" role. However, if I re-apply the plan, the first of the two returns to the Global Permissions settings but the second is skipped. If applied a tird time, it resets to te correct state. And additioanal runs flip between the two. Next, if I run a terraform destroy, it will remove the state as excepted but with additional errrors as mentioned in the initial summary of this issue.
Ryan |
I'm also experiencing this issue. Has anyone found a fix or workaround? |
vsphere_entity_permissions
- global permissions preventing removing root folder permissions
This bug has been open for almost two years now. Just wondering how people are working around this without a fix in place? |
Manually cleaning up the role (or through some other automation) and then removing the role/vsphere_entity_permissions from the terraform state: |
My team has just stopped trying to use this resource - we look at alternative methods of provisioning access. |
There are underlying issues with the implementation that require further development efforts on this resource (and other IAM-related items). However, there are upstream dependencies \that would need to be exposed by govmomi. On the VMware side (this provider is maintained by HashiCorp) we are looking to contribute these features/fixes in the future based on prioritization. Ryan Johnson |
Terraform Version
Terraform v0.15.1
vSphere Provider Version
1.26.0
Affected Resource(s)
vsphere_entity_permissions
Terraform Configuration Files
Debug Output
https://gist.github.com/slarimore02/dadd86f45cad33bda0905200ce177d84
Expected Behavior
When running terraform destroy the vsphere_entity_permissions resource should be removed for the root vSphere folder. The provider should only remove/create permissions defined in the vsphere_entity_permissions resource not existing Global Permissions.
Actual Behavior
When running terraform destroy the vsphere_entity_permissions resource is not deleted. The root folder inherits all of the users/permissions defined in the Global Permissions and the provider cannot find those additional permissions to remove.
The error below is returned:
Error: error while deleting permission for the user/group VSPHERE.LOCAL\Administrator ServerFaultCode: The object or item referred to could not be found.
Steps to Reproduce
Important Factoids
vSphere version 7.0.0.10100
Community Note
The text was updated successfully, but these errors were encountered: