[FEATURE]Improved error message while handling drift in subaccounts related to entitlements

[CHERIANS]

What area do you want to see improved?

terraform provider

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

As user after creating a BTP Subaccount via Terraform might make manual changes to subaccount configuration related to entitlements. While performing a terraform destroy the delete operation fails as expected. But its difficult to identify the cause of failure from the error message. Can we have more friendly error message which describes or provides reason for destroy operation failure

Describe the solution you would like

An enduser might create a subaccount by running the BTP terraform provider. After the execution of script he might have gone and manually enabled CF. While doing a destroy the operation fails as terraform is unable to set the quota of CF runtime to zero from one. Can a friendly message be shown that CloudFoundry runtime is enabled and this is not managed by Terraform.

Describe alternatives you have considered

No response

Additional context

No response

[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.