Create and Assign non-admin roles to users

CD-as-a-ServiceFeature
undefined
undefined

It is now possible to create roles and assign users to those roles. You can now restrict access to configuration tab - secrets, privilege to invite new users, integrations within the CD-as-a-Service portal. Creating roles can be done by creating an armory config file as shown below. Documentation for the feature is still in progress, but you can use the syntax shown here to create new roles.

roles:
    - name: Potato Facts Role
      tenant: main
      grants:
        - type: api
          resource: deployment
          permission: full
  - name: Potato Lies Role
    tenant: main
    grants:
      - type: api
        resource: organization
        permission: full

The file can live in your source control and be applied to armory by using the armory CLI command armory config apply -f config.yaml

Users can be assigned roles when they are being invited, or can be assigned new roles from the Users tab. Only admin users can view the Configuration tab in the CD-as-a-Service UI.

Users signing in with SSO will get the permissions of any roles that have the same name as one of their groups.

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