[BUG] Error when re-creating entitlements that only require enablement

[EliasB17]

Is there an existing issue for this?

• I have searched the existing issues

What version of the Terraform exporter are you using?

1.4.0

What version of the Terraform CLI/OpenTofu CLI are you using?

1.13.3

What type of issue are you facing

bug report

Describe the bug

When re-creating entitlements from an exported configuration, an error occurs if the entitlement only requires enablement but was exported with a quota value.
This is caused by the default behavior of the exporter, which includes a quota amount for all entitlements — even those that only need to be enabled.

Error Message:
The enable parameter has not been set or the amount parameter was set with a quota value (setting a quota is not supported by multitenant applications and by services that do not permit a numeric quota assignment). [Error: 12003/400]

Expected Behavior

The exporter should differentiate between quota-based and enablement-only entitlements to avoid invalid configurations.

Steps To Reproduce

1. Export entitlements from a subaccount using the exporter.
2. Include an entitlement that only requires enablement (no quota).
3. Use the exported configuration to re-create the entitlement via the Terraform SAP BTP Provider
4. Observe the error during re-creation.

User's Role Collections

• Global Account Administrator
• Subaccount Administrator

Add screenshots to help explain your problem

Additional context

I'm currently using a trial account.
If you manually remove the amount attribute from the exported configuration, the entitlement can be successfully re-created.

[lechnerc77]

Nees to be validated if the requiremnt for amount can be validated/cheked based on the platform information

[lechnerc77]

First Analysis:

• The platform API always returns a value for the quota independent if the quota/amount is needed or not.
• Consequence: The generated Terraform code uses the READ operation to fill the fields. As it receives a non-zero result for the quota it will add it to the configuration.

There is an option to distinguish the different types of services, based on the API according to the documentation using the category field (computed):

• PLATFORM: A service required for using a specific platform; for example, Application Runtime is required for the Cloud Foundry platform.
• SERVICE: A commercial or technical service. that has a numeric quota (amount) when entitled or assigned to a resource. When assigning entitlements of this type, use the 'amount' option instead of 'enable'. See: PUT/entitlements/v1/directories/{directoryGUID}/assignments.
• ELASTIC_SERVICE: A commercial or technical service that has no numeric quota (amount) when entitled or assigned to a resource. Generally this type of service can be as many times as needed when enabled, but may in some cases be restricted by the service owner. When assigning entitlements of this type, use the 'enable' option instead of 'amount'. See: PUT/entitlements/v1/directories/{directoryGUID}/assignments.
• ELASTIC_LIMITED: An elastic service that can be enabled for only one subaccount per global account.
  APPLICATION: A multitenant application to which consumers can subscribe. As opposed to applications defined as a - 'QUOTA_BASED_APPLICATION', these applications do not have a numeric quota and are simply enabled or disabled as entitlements per subaccount.
• QUOTA_BASED_APPLICATION: A multitenant application to which consumers can subscribe. As opposed to applications defined as 'APPLICATION', these applications have an numeric quota that limits consumer usage of the subscribed application per subaccount. When maxAllowedSubaccountQuota is > 0, this is the limit that can be set when assigning the max quota entitlement of the app to any subaccount. If maxAllowedSubaccountQuota is = 0 or null, the max quota that can be entitled to any subaccount is the amount purchased by the customer (the global account quota).
• ENVIRONMENT: An environment service; for example, Cloud Foundry.

Next steps:

• Validate provider implementation of resource to check response data
• Depending on outcome discuss solution options (change in provider, filtering in exporter based on category)

[lechnerc77]

Response data of provider: API returns non-NULL amount independent of entitlement category.

Option: change provider behavior based on category i.e. transfer amount depending on category. This means that a provider schema migration must be implemented to fix existing states (see https://developer.hashicorp.com/terraform/plugin/framework/migrating/schema)

[lechnerc77]

The root cause for this issue will be fixed in the Terraform provider for SAP BTP (see SAP/terraform-provider-btp#1209).
Once the PR is merged and a new release of the provider is available we will upgrade the exporter to use the version of the Terraform provider for SAP BTP.

As this will take a bit, please use the workaround of manually removing the amounts for services and applications that do not have a quota