Deploy Environment

initiate a new deployment for a specific environment this step will initiate the environment deployment and will not wait for deployment to finish environment deployment will continue running asynchronously you can monitor deployments directly from in the portal under environments and/or slack syntax microtica yaml steps step name type deploy target environment env id dev rft43 branch filter master parameter description required title the display name of the step no type the type of the microtica built in step should always be deploy for this type of step yes target should always be environment for this type of step yes env id the id of the environment to initiate deployment for yes branch filter initiate deployment only for commit/manual trigger on specified branch if not specified, deployment will be initiated on every pipeline execution e g develop, feature/upgrade eks etc no partial initiate deployment for specific environment resources with their respective version partial deployment is useful for continuous delivery of infrastructure components where each component has its own pipeline syntax create missing resources true|false resource version overrides \<name of the environment resource> \<version to be deployed> no initiate deployment on existing environment in the following example we package a cfn template into microtica component that was previously added into the environment this will basically package a new version of the component and initiate environment deployment microtica yaml steps clone title clone my source code from git type git clone package title package my cfn template into microtica component type cfn component cfn template template json deploy type deploy target environment env id dev 5zkjhq8apy given the above configuration, deployment will be triggered on environment with id dev 5zkjhq8apy on every pipeline execution initiate deployment for specific branch microtica allows you to orchestrate environment deployments based on git branch the pipeline was trigged for both commit and manual trigger this is very useful for trunk based development https //trunkbaseddevelopment com/ where for each environment you maintain separate branch commit on each branch will build the component source code from that branch and trigger deployment on the appropriate environment microtica yaml steps clone title clone my source code from git type git clone package title package my cfn template into microtica component type cfn component cfn template template json deploy type deploy target environment env id dev 5zkjhq8apy branch filter develop given the above configuration, deployment will be triggered on environment with id dev 5zkjhq8apy only if the pipeline was triggered from branch develop