Deployment pipeline more agile between dev and test, and approval between test and prod?

[Mikael Karlsson]

Hi, just started with AES and AEMC and some questions have come up.

How could we configure Deployment Pipeline / AEMC to allow our developers to publish between Dev and Test without any approval? This could happen multiple times before finally deciding to deploy to production, i can't see that they have the option to choose if they intend the submission for test or prod.

Consider something like this which must be common:

1. Submit app in Dev
   1. Approval is created for deployment Dev-Test
      1. Approved, app installed into Test, approval task automatically created for Test-Prod
   2. Developer finds bug in Test which needs fixing in Dev (but the production deployment request is still pending and will be pushed to Prod if approved, how can the developer prevent this)

[Mikael Karlsson · Accepted solution]

I'll try to conclude the thread, today there seems to be no OOTB way to designate if the app submission should go all the way to production or if the submission was just part of normal dev-test procedure. To accomplish what we are looking for we will likely have to modify the existing flow or adding a wrapper control flow to automatically handle the approvals based on data which is available in the deployment request. Perhaps a good feature request for the long run would be to surface the choice of the approval flow just like it's done for the App Service creation subflow to stay clear of customizing the shipped flows.

[Artur ___kiews2]

@Mikael Karlsson this is something that we want to do also shortly. For example, I did 5 minor releases on prod 2 weeks ago for one of our apps because I forgot to remove things like alerts, logs, etc...
Unfortunately, we are still discussing how to do that from a process and implementation perspective. If we have a solution I will try to share it with you here

[Edoardo M]

Hi @Mikael Karlsson,
Thank you for your precious insights and discoveries in this thread. I agree with your proposal, so why don't you post this idea in the portal? It will be evaluated by the App Engine PM. Thanks a lot!