SimonXming / concourse-vault-resource

Concourse resource to fetch secrets from Vault on an EC2 instance.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Vault Resource

Reads secrets from Vault. Authentication is done (by default) using the Token method, which must be configured before using this resource. It can also use the AppRole method to authenticate.

Source Configuration

  • url: Optional. The location of the Vault server. Defaults to https://vault.service.consul:8200.

  • paths: Optional. If specified (as a list of glob patterns), only changes to the specified files will yield new versions from check.

  • token: Optional. Use a Token to authenticate. This parameter is used only with auth_method: Token.

  • expose_token: Optional. If specified, this option will expose the token to make it available to other resources

  • auth_method: Optional. By default will use the Token method. If AppRole is specified, it will read the role_id and secret_id parameter to authenticate on the approle endpoint. If github is specified it will read the github_personal_access_token parameter.

  • role_id: Optional. Use a specific role id to authenticate. This parameter is used only with auth_method: AppRole.

  • secret_id: Optional. Use a specific secret id to authenticate. This parameter is used only with auth_method: AppRole.

  • github_personal_access_token: Optional. Use a GitHub personal access token to authenticate. This parameter is used only with auth_method: GitHub.

  • tls_skip_verify: Optional. Skips Vault SSL verification by exporting VAUKT_SKIP_VERIFY=1.

Example

Resource configuration using Token authentication:

resources:
- name: vault
  type: vault
  source:
    url: https://secure.legitcompany.com:8200
    auth_method: Token
    token: xxxxxxxxxxxx

Resource configuration using AppRole authentication:

resources:
- name: vault
  type: vault
  source:
    url: https://secure.legitcompany.com:8200
    auth_method: AppRole
    role_id: e6889709-5ff8-c670-a083-79f1c5035709
    secret_id: e6889709-5ff8-c670-a083-79f1c5035709

Fetching secrets:

- get: vault
  params:
    paths:
      - secret/build/git
      - secret/build/aws/s3

Behavior

check: Check for new versions.

Essentially a noop, the current date is always returned as {"date": "$DATE"}

in: Read secrets from Vault

Reads secrets from Vault and stores them on disk as JSON files.

The path of the secret will match the path on disk - ie in the example above, vault/build/git.json and vault/build/aws/s3.json will be created.

Parameters

  • paths: Required. List of paths to read from the Vault secret mount.

About

Concourse resource to fetch secrets from Vault on an EC2 instance.

License:MIT License


Languages

Language:Shell 84.3%Language:Dockerfile 15.7%