Skip to content
This repository has been archived by the owner on Feb 13, 2024. It is now read-only.

[FEATURE REQUEST] Change subdomain nameing #260

Closed
1 task done
AlexRieder opened this issue Oct 17, 2022 · 3 comments
Closed
1 task done

[FEATURE REQUEST] Change subdomain nameing #260

AlexRieder opened this issue Oct 17, 2022 · 3 comments
Labels
available in dev fix/enhancement is available in dev enhancement New feature or request
Milestone

Comments

@AlexRieder
Copy link
Contributor

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?

  • Yes, I would like to support you

Anything else?

No response

@AlexRieder AlexRieder added the enhancement New feature or request label Oct 17, 2022
@lechnerc77 lechnerc77 moved this to Backlog in btpsa planning Nov 16, 2022
@rui1610
Copy link
Contributor

rui1610 commented Nov 18, 2022

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?

@AlexRieder
Copy link
Contributor Author

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.

@lechnerc77 lechnerc77 added this to the to be planned milestone Mar 7, 2023
@lechnerc77 lechnerc77 moved this from Backlog to Done in btpsa planning Mar 7, 2023
@lechnerc77 lechnerc77 added the available in dev fix/enhancement is available in dev label Mar 7, 2023
@lechnerc77 lechnerc77 modified the milestones: to be planned, btpsa-v1.6.0 Mar 7, 2023
@lechnerc77
Copy link
Member

Merged into main

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
available in dev fix/enhancement is available in dev enhancement New feature or request
Projects
No open projects
Status: Done
Development

No branches or pull requests

3 participants