Added support for Blue/Green Deployment Strategies

CD-as-a-ServiceFeature
undefined
undefined

Watch the demo to learn more

  • Specify blueGreen as a strategy for environments.

  • Specify redirectTrafficAfter as a set of constraints. This allows you to define constraints that must be fulfilled before the next version of the application starts receiving traffic. For Example, you can require that the next version will not receive traffic before a manual approval has been issued.

  • Specify shutDownOldVersionAfter as a set of constraints. This allows you to define constraints that must be fulfilled before the old version of the application is scaled down.

  • Added a new template for the Blue/Green deployment strategy.

  • Here is a docs guide to get started on how to use Blue/Green deployment strategy

Known Issues

  • View Environment link sometimes does not redirect to a new page. To work around the issue, you can edit the URL in the address bar by deleting console.cloud.armory.io/deployments/

  • Multiple manual approvals in a single constraint currently returns an error. This limits the redirectTrafficAfter and shutDownOldVersionAfter constraints to a single manual approval each.

Armory logo

Armory

VisitFollow us on X

Nov

28

Sep

29

Cover image

Pipeline graph is now available when deploying to a single target

CD-as-a-ServiceFeature

Certain functionality, such as trigger nodes and the ability to redeploy an old version, are only available on the pipeline graph. With this change these features are available when deploying to a single target.

New
  • Added support for pipeline view during deployments to a single target for easier visual tracking.

Sep

15

New on the deployment graph: Deployment triggers with source context!

CD-as-a-ServiceFeature
undefined
undefined

We've added a new element to the deployment graph called a Trigger Node which explains how a deployment was triggered by displaying the source system, initiating person, and trigger type. This allows anyone on the team to immediately know the source of a deployment, including who triggered it, and how it maps back to a pull request or commit.

When triggering from GitHub, additional source details will appear on the Trigger Node: PR title, PR number, commit SHA, branches, and in the event of a push tag trigger, the associated tag. Each element in the Source section is a deep link back to GitHub.

If context variables were passed with the trigger, they will appear in a Context Variables section on the Trigger Node.

Trigger Nodes will automatically show up on your deployment pipelines. Customers who have already configured a GitHub Action will need to adjust the workflow token permissions in their configuration to view the full set of Source Context information. This can be accomplished by adding a permissions block to your workflow, and adding a token to the GitHub action's env block.

Please refer to the updated documentation pages for more information.
Monitor Deployments

Use Armory's GitHub Action to Deploy Your App Using CD-as-a-Service

permissions:
  contents: read
  pull-requests: read
  statuses: read

# Add GH_TOKEN to env in the cli-deploy-action step
- name: Deploy
  env:
      GH_TOKEN: '${{ secrets.GITHUB_TOKEN }}'
  uses: armory/cli-deploy-action@main