Reserve Manual Approvals to specific roles

CD-as-a-ServiceFeature
undefined
undefined

You can now restrict which roles can issue manual approvals during the course of deployment. This helps you ensure that only authorized people are promoting changes to Production, and application owners are interacting with their own applications. To restrict approvals, you need to add a requiresRoles field in the manual approval step and list the roles that can issue approvals. Organization Admins and respective tenant's Admins can issue approvals, even if those roles are not included in the requiresRoles field.
Users without the required role will have the approval functionality disabled and will see a message on which roles can issue approvals. More detailed documentation is in progress and will soon be up on our docs site.

targets:
  prod:
    account: demo-prod-cluster
    namespace: application-1
    strategy: canary-20
    constraints:
      beforeDeployment:
        - pause:
            untilApproved: true
            requiresRoles: ["Production Owner"]
strategies:
  canary-20:
    canary:
      steps:
        - setWeight:
            weight: 20
        - pause:
            untilApproved: true
            requiresRoles: ["sample-application-owners"]
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