Design common ADO deployment yaml pipeline template flexible and scalable
Current template doesn’t allow to inject extra task/step for a specific microservice within existing stage of ADO release pipeline template. Example: Schema service needs to run a bootstrap script task right after its deployment in an existing environment (ADO release stage) which can’t be done within any of its existing stage (dev, qa, prd, etc.). Instead we have to add an extra stage (not a good practice and shown below in attachment) in ADO release pinene as temporary workaround. Please refer to attached screenshot for more understanding.
Example template link: https://community.opengroup.org/osdu/platform/deployment-and-operations/infra-azure-provisioning/-/blob/master/devops/deploy-stages.yml