-
Notifications
You must be signed in to change notification settings - Fork 3
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
[BUG] Assignment of roles on space level fail #69
Comments
Should be fixed with #64 |
Don't think so as it seems that the roles are not recognized. |
Actually, one has to either fill in a space or an org guid, and accordingly pick an org or space role to assign for that particular user. Since validation for role types is in a custom validateConfig and for the space/org conflict is present in the attributes, both are getting triggered simultaneously which is a bug. You should be able to notice something similar to this too at the end for the above input
Since we plan on splitting this role resource to space_role and org_role according to #64, this issue should be tackled. |
Signed-off-by: Ray <[email protected]>
Signed-off-by: Ray <[email protected]>
Signed-off-by: Ray <[email protected]>
Signed-off-by: Ray <[email protected]> Co-authored-by: Ray <[email protected]>
Signed-off-by: Ray <[email protected]> Co-authored-by: Ray <[email protected]>
Is there an existing issue for this?
What version of the Terraform provider are you using?
main-branch
What version of the Terraform CLI are you using?
1.7.3
What CF API version are you using?
3.153
What type of issue are you facing
bug report
Describe the bug
When assigning a role on space level, I get the following error:
However according to the documentation the used types are available.
Expected Behavior
The roles can be assigned on space level
Steps To Reproduce
Usual flow
terraform apply
Your Terraform Configuration
Roles
I also tried it with manually assigning me the Space Manager role, but that did not change the error
Add screenshots to help explain your problem
n/a
Additional context
n/a
The text was updated successfully, but these errors were encountered: