Armory CLI Version 0.13.1

Bug FixCD-as-a-Service

Armory CLI Version 0.13.1

Important note: You must be on AVM v1.0.2 to install this and all later CLI versions.

What's New?

  • Adds support for deploying to multiple environments. Watch the demo to learn more! 

    • Specify dependsOn constraints for environments. This constraint allows you to require that certain environments deploy before other environments when deploying to multiple environments.

    • Specify beforeDeployment constraints for an environment. This constraint allows you to require a manual approval before a particular environment. For example, you can require that a deployment to production cannot start until prior environments, such as testing and staging, have completed.

    • Read more about the new constraints in the deployment file reference.

  • Add flag that allows for setting application name outside of deployment yaml. If you specify the --application argument when starting a deployment, you can now override the name of the application that is specified in the deploy.yml. This can be useful if you have a single deploy.yml that is otherwise applicable to multiple applications.

Known Issues

  • (Fixed in 0-.13.2) When using a deployment constraint of type beforeDeployment, you must also provide a 'dependsOn' constraint. If you do not, the CLI crashes with a segmentation fault when starting the deployment. As a workaround, add a dependsOn constraint that is an empty array. constraints:     dependsOn: []

  • When using a beforeDeployment constraint that is a manual approval, the deployment details on the right panel of the screen doesn't automatically update to show the details of that deployment to that environment when you approve the deployment. To workaround the issue, close and reopen the panel.

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