The above adds to the CircleCI workflow two things:
Consumes a context called djd-starter-kit-s3-deploy (this is created in both CircleCI orbs with the same environment variable, DOPPLER_TOKEN, that is able to access the ci environment in a Doppler project called djd-starter-kit-s3-deploy containing the AWS S3 deployment secrets needed by g-deploy)
Installs the Doppler orb
Uses the DOPPLER_TOKEN env var from the CircleCI context to run g-deploy using Doppler secrets
…The idea is that we store the usual S3 deployment-related secrets in Doppler from here on out. This would totally obviate the need to ever do buildbot reinit and vastly simplify rotating secrets.
The above adds to the CircleCI workflow two things:
djd-starter-kit-s3-deploy(this is created in both CircleCI orbs with the same environment variable,DOPPLER_TOKEN, that is able to access thecienvironment in a Doppler project calleddjd-starter-kit-s3-deploycontaining the AWS S3 deployment secrets needed by g-deploy)g-deployusing Doppler secrets…The idea is that we store the usual S3 deployment-related secrets in Doppler from here on out. This would totally obviate the need to ever do
buildbot reinitand vastly simplify rotating secrets.