You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 13, 2024. It is now read-only.
Currently the subdomain of a subaccount is created by using the display name and adding the global account id as suffix. For our usecase this can lead to problems while creating the api rule in kyma as we use the subdomain as name of the api rule which is exceeding more than 63 characters.
Have you tried providing the subdomain via the subdomain parameter in the parameters.json file? That should help you.
Can you please try out and let us know whether this addressed your issue?
I can give it a try and most likely this is going to solve the problem. The downside of that approach would be that the subdomain would need to be given as parameter whenever the script is called as it needs to be unique on the landscape which means we cannot provide it within the parameters.
Which area is mainly impacted
Configuration
Requested Feature
Currently the subdomain of a subaccount is created by using the display name and adding the global account id as suffix. For our usecase this can lead to problems while creating the api rule in kyma as we use the subdomain as name of the api rule which is exceeding more than 63 characters.
Use Case/Scenario
https://github.com/SAP-samples/btp-setup-automator/tree/main/usecases/released/discoverycenter/3638-kyma-multitenant
https://github.com/SAP-samples/btp-setup-automator/tree/main/usecases/released/discoverycenter/3999-kyma-day2-operations
https://github.com/SAP-samples/btp-setup-automator/tree/main/usecases/released/discoverycenter/4000-kyma-identity-management
Would you like to support us?
Anything else?
No response
The text was updated successfully, but these errors were encountered: