AEMC/Deployment Pipeline Automatic Application Service creation naming convention?

[Mikael Karlsson]

By default, the App Service CI which gets created by the default flow has the version appended to the name, for example "Managed Resource Objects@2.0.0". This means that each deployment and change request will create a new unique CI which i feel is very weird. I have plans to copy the default flow and instead create the CIs without the version in the name and therefore be able to track the same application over time. Seeing which change requests for deployment has happened etc. I'm just looking for input here in case there might be something essential to the CSDM which i've not foreseen or if the default implementation perhaps also feels weird to others as well.

[WORKFLOW-COWBOY · Accepted solution]

Hi @Mikael Karlsson, 

It was explained to me that this was an intentional choice of how the product was developed. It is my understanding that it should create a Business CI that is the parent for each of the App CIs that gets created. 

My assumption is that it is likely possible to modify the default Pipeline Flows to change this behavior if desired. 

[Mikael Karlsson]

Thanks @WORKFLOW-COWBOY , that seems to be the case, i can see now that there is a business application above. Ok then it makes more sense. Yup they provide a template flow for detecting existing or new CI which can be copied and configured if we wish.