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

YAML

steps:
  step-name:
    type: deploy
    target: environment
    env_id: DEV-rft43
    branch_filter: master
ParameterDescriptionRequired
titleThe display name of the step.No
typeThe type of the Microtica built-in step.
Should always be deploy for this type of step.
Yes
targetShould always be environment for this type of step.Yes
env_idThe ID of the environment to initiate deployment for.Yes
branch_filterInitiate 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

#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.

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.

You can find the environment ID in environment details page.

Environment details

#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 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.

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.