As follow up of https://github.com/kyma-project/application-connector-manager/issues/290#issuecomment-2373401152, we have to ensure that ACM is handling multuple applications with the same name properly (e.g. two different customers create an application ans use the same name). The ACM has to make sure that an application name will always be unique, e.g. by adding a random suffix/prefix.
AC:
[ ] ACM accepts different applications with the same name. Internally, they are treated as different applications and receive a unique name but the customer visible application name is the originally provided name.
[ ] Unit tests are verifying that ACM is capable to deal with several applications with the same name but distinguishes them internally properly.
Reasons
Caused by changes in the UCL API, the ACM becomes responsible to ensure uniqueness of application names.
Description
As follow up of https://github.com/kyma-project/application-connector-manager/issues/290#issuecomment-2373401152, we have to ensure that ACM is handling multuple applications with the same name properly (e.g. two different customers create an application ans use the same name). The ACM has to make sure that an application name will always be unique, e.g. by adding a random suffix/prefix.
AC:
Reasons
Caused by changes in the UCL API, the ACM becomes responsible to ensure uniqueness of application names.
Attachments