EXECUTE_PRIORITY.md

Execute Step Priority

I. Create, Update, or Deploy

When creating or updating resources, execute steps should occupy certain priority ranges to ensure creation happens in the required sequential order. 0 - 190 should be kept clear for Azure Tools common execute steps (e.g. VerifyProvidersStep, ResourceGroupCreateStep, etc.).

1. Managed Environment

Priority Range: 200 - 290

Steps

• LogAnalyticsCreateStep: 220
• ManagedEnvironmentCreateStep: 250

2. Azure Container Registry

Priority Range: 300 - 390

Steps

• RegistryCreateStep: 350

3. Image

Priority Range: 400 - 490

General Steps

Build Image in Azure Steps

• TarFileStep: 420
• UploadSourceCodeStep: 430
• RunStep: 440
• BuildImageStep: 450
• ContainerRegistryImageConfigureStep: 470

Container Registry Steps

• ContainerRegistryImageConfigureStep: 470

updateImage Steps

• UpdateRegistryAndSecretsStep: 480
• UpdateImageStep: 490 (revision draft)

4. Unallocated Space

Priority Range: 500 - 590

Steps

Reserved

5. Container App

Priority Range: 600 - 690

Steps

• ContainerAppCreateStep: 620
• ContainerAppUpdateStep: 650

6. Ingress

Priority Range: 700 - 790

Steps

• EnableIngressStep: 750 (update existing container app)

• DisableIngressStep: 750 (update existing container app)

• TargetPortUpdateStep: 750 (single command only)

• ToggleIngressVisibilityStep: 750 (single command only)

7. Secrets

Priority Range: 800 - 890

Steps

• SecretCreateStep: 820
• SecretUpdateStep: 850

8. Unallocated Space

Priority Range: 900 - 1090

Steps

• Reserved for future commands TBD.

9. Scaling

Priority Range: 1100 - 1190

Steps

• AddScaleRuleStep: 1120 (revision draft)

10. Unallocated Space

Priority Range: 1200 - 1390

Steps

• Reserved for future commands TBD.

11. Deploy

Priority Range: 1400 - 1490

Steps

• DeployRevisionDraftStep: 1450

II. Delete Steps

TBD... Note: When deleting resources, typically the priority ranges will change as the dependencies are inverted when compared to the create steps.