Add New Context Variables at Deploy Time

How to add new context variables

You can add new context variables at deployment time by using the --add-context argument on the command line or from within your Armory CD-as-a-Service GitHub Action. CD-as-a-Service adds the new context variables to webhook triggers and canary analysis steps in any deployment constraint.

The value of the --add-context argument is a comma-delimited list of key=value pairs.

For this example, you want to add the following new context variables:

Your command line looks like this:

armory deploy start -f deploy.yml --add-context=smokeTest=true,environment=prod,changeBy=jane-doe

In your GitHub Action, you add an addContext key in your Deployment step.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

name: Deploy my latest version

on:
  push:
    branches:
      - main  

jobs:
  build:
    name: deploy from main
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - name: Deployment
        uses: armory/cli-deploy-action@main
        with:
          clientId: "${{ secrets.CDAAS_CLIENT_ID }}"
          clientSecret:  "${{ secrets.CDAAS_CLIENT_SECRET }}"
          path-to-file: "/deploy.yml"
          addContext: "smokeTest=true,environment=prod,changeBy=jane-doe"
          applicationName: "potato-facts"

Known issues

Context variables are not added in the following situations:

• An analysis step when used in an after deployment constraint
• A step in a blue/green deployment strategy