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.).
Priority Range: 200 - 290
- LogAnalyticsCreateStep: 220
- ManagedEnvironmentCreateStep: 250
Priority Range: 300 - 390
- RegistryCreateStep: 350
Priority Range: 400 - 490
- TarFileStep: 420
- UploadSourceCodeStep: 430
- RunStep: 440
- BuildImageStep: 450
- ContainerRegistryImageConfigureStep: 470
- ContainerRegistryImageConfigureStep: 470
- ContainerAppUpdateStep: 480 (Todo - investigate decoupling this command from imageSource when revision draft update support is added)
Priority Range: 500 - 590
Reserved
Priority Range: 600 - 690
-
EnableIngressStep: 650
-
DisableIngressStep: 650
-
TargetPortUpdateStep: 650 (single command only)
-
ToggleIngressVisibilityStep: 650 (single command only)
Priority Range: 700 - 790
- ContainerAppCreateStep: 750
Priority Range: 800 - 890
- SecretCreateStep: 820
- SecretUpdateStep: 850
Priority Range: 900 - 1090
- Reserved for future commands TBD.
Priority Range: 1100 - 1190
- ScaleRangeUpdateStep: 1110
- AddScaleRuleStep: 1120
Priority Range: 1200 - 1390
- Reserved for future commands TBD.
Priority Range: 1400 - 1490
- DeployRevisionDraftStep: 1450
TBD... Note: When deleting resources, typically the priority ranges will change as the dependencies are inverted when compared to the create steps.