CircleCI Ideas

Allow environment variables beyond the run: key commands

I would like to use environment variables in values outside of the run: key. For example:

- image: circleci/python:2.7.14
I would like to define the image name as - image: circleci/${DOCKER_IMAGE_NAME}
Lots of customers at AWs re:invent 2018 were asking for this enhancement.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Nov 28 2018
  • New
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    November 28, 2018 22:09

    That particular use case won't be possible because the env vars aren't present before the job runs, but we are looking at ways to expose more config-time variables (and/or make a cleaner distinction between sensitive env vars that are only in the runtime vs. project variables we can expose during config processing)