[FEATURE] Error message when Org Manager Role is missing

[lechnerc77]

What area do you want to see improved?

terraform provider

Is your feature request related to a problem? Please describe.

On SAP BTP the user often has access to the org ID in the cockpit even if not having the role org_manager assigned.

This could lead to errors when using data sources or resources form the provider. The error message when accessing the org then states:

Error: API Error Fetching Organization
│
│ with data.cloudfoundry_spaces.all,
│ on main.tf line 1, in data "cloudfoundry_spaces" "all":
│ 1: data "cloudfoundry_spaces" "all"{
│
│ Could not get details of the Organization with ID 123455 :
│ error executing GET request for /v3/organizations/12345:
│ cfclient error (CF-ResourceNotFound|10010): Organization not found
╵

This can be quite confusing

Describe the solution you would like

It would be good if the error message would contain a hint that this might be due to missing org manager role assignments

Describe alternatives you have considered

n/a

Additional context

n/a

[github-actions]

Thanks for the feature request. We evaluate it and update the issue accordingly.

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post 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.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[Dray56]

Hi @lechnerc77 ,

That is a nice suggestion you have made but this problem is from Cloudfoundry design itself. It gives the same response of not found from the API when the resource actually does not exist or if someone does not have sufficient privileges to view the resource. There is no way to differentiate from an API perspective for the 2 paths. Therefore, general thumb rule which CF practitioners apply is when they face this error, they ensure whether they have sufficient privileges like organization_user, organization_manager, space_manager, space_developer etc based on the need and even after obtaining the privileges and trying to fetch a particular resource, if the error is appearing that implies that the resource truly does not exist. There is no workaround for that.