---

SecretHub has joined 1Password! Find out more on the SecretHub blog. 🎉

---

CircleCI Orb

No more copy-pasting sensitive values into a GUI. Securely load secrets into CircleCI and sync them automatically.

This Orb is officially supported and actively maintained by SecretHub, but community contributions are very welcome.

Usage

To execute a command that needs secrets, replace your CircleCI run command with secrethub/exec. You can make secrets available to your command as environment variables by referencing their SecretHub path, prefixed by secrethub://:

version: 2.1
orbs:
  secrethub: secrethub/cli@1.1.0

jobs:
  deploy:
    docker:
      - image: cimg/base:stable
    environment:
      AWS_ACCESS_KEY_ID: secrethub://company/app/aws/access_key_id
      AWS_SECRET_ACCESS_KEY: secrethub://company/app/aws/secret_access_key
    steps:
      - checkout
      - secrethub/exec:
          command: |
            echo "This value will be masked: $AWS_ACCESS_KEY_ID"
            echo "This value will be masked: $AWS_SECRET_ACCESS_KEY"
            ./deploy-my-app.sh
workflows:
  deploy:
    jobs:
      - deploy

Alternatively, you can set the shell of the native CircleCI run command:

version: 2.1
orbs:
  secrethub: secrethub/cli@1.1.0

jobs:
  deploy:
    docker:
      - image: cimg/base:stable
    steps:
      - secrethub/install
      - checkout
      - run:
          shell: secrethub run -- /bin/bash
          environment:
            AWS_ACCESS_KEY_ID: secrethub://company/app/aws/access_key_id
            AWS_SECRET_ACCESS_KEY: secrethub://company/app/aws/secret_access_key
          command: |
            echo "This value will be masked: $AWS_ACCESS_KEY_ID"
            echo "This value will be masked: $AWS_SECRET_ACCESS_KEY"
            ./deploy-my-app.sh
workflows:
  deploy:
    jobs:
      - deploy

You can either set the shell on the run command level, or you can set it on the job level to use it for every step in the job. That way you can also load secrets into other orbs:

version: 2.1
orbs:
  aws-cli: circleci/aws-cli@0.1.20
  secrethub: secrethub/cli@1.1.0

jobs:
  deploy:
    executor: aws-cli/default
    shell: secrethub run -- /bin/bash
    environment:
      AWS_DEFAULT_REGION: us-east-1
      AWS_ACCESS_KEY_ID: secrethub://company/app/aws/access_key_id
      AWS_SECRET_ACCESS_KEY: secrethub://company/app/aws/secret_access_key
    steps:
      - secrethub/install
      - checkout
      - aws-cli/setup

workflows:
  deploy:
    jobs:
      - deploy

See the src/examples directory for more examples.

Masking

When using either the secrethub/exec orb command or the secrethub run shell wrapper, all secrets are automatically masked from the CI log output. If secrets (accidentally) get logged, they will be replaced with:

<redacted by SecretHub>

Authentication

For your CircleCI jobs to authenticate to SecretHub and decrypt the secrets they need, create a SecretHub service account, give it read access to the secrets it needs, and configure the credential as SECRETHUB_CREDENTIAL in your CircleCI project settings or Context environment variables.