anaconda-graveyard / conda-concourse-ci

Conda-driven Concourse CI for package building
BSD 3-Clause "New" or "Revised" License
13 stars 29 forks source link

Use intermediate key from vault #116

Closed soapy1 closed 5 years ago

soapy1 commented 5 years ago

As per https://github.com/pivotalservices/concourse-pipeline-samples/tree/master/concourse-pipeline-patterns/vault-integration you can update jobs to use vault by just changing variables in the config file.

Since the intermediate-private-key is used elsewhere in c3i, it needs to stay in the variables config file for now. But, with this change the key won't be uploaded every time.

Example part of a build:

groups: []
resources:
- name: rsync-recipes
  type: rsync-resource
  source:
    base_dir: /ci/imagesize-feedstock/plan_and_recipes
    disable_version_path: true
    private_key: ((common.intermediate-private-key))
    server: bremen.corp.continuum.io
    user: ci

related to https://github.com/ContinuumIO/automated-build/pull/11