We have integrated DAP with our PCF environment and users are using Summon to map their secrets. In the interest of code portability, our customers would like to use the same secrets.yml file in QA and Production. Our secrets.yml file looks like this:
AAP_PASS: !var $ENVIRONMENT-CyberArkVault/PCF/DAP_PCF_STAC/AppAuthPersistence_Password/password
VLO_ID: !var $ENVIRONMENT-CyberArkVault/PCF/DAP_PCF_STAC/VarianceLogOAuth_ClientID/password
VLO_SECRET: !var $ENVIRONMENT-CyberArkVault/PCF/DAP_PCF_STAC/VarianceLogOAuth_ClientSecret/password
We have tried setting the ENVIRONMENT variable in manifest.yml and also using ‘cf set-env’, but are having no luck. Has anyone gotten something similar to work? I see this on the Conjur buildpack page that seems to indicate that it can. GitHub - cyberark/cloudfoundry-conjur-buildpack: Buildpack for the Conjur / Cloud Foundry integration