Allow environment variables to be used in auth.json #11746
Comments
|
I suppose that I could generate the full |
|
Since we already support Supporting ENV variables inside configuration files is not a trivial feature. A pull request could go a lot further than a simple 'request for a change'. |
|
Right we do support COMPOSER_AUTH for now that's your best option, you could still define it dynamically in your zshenv using other env vars as input I assume, so that you don't duplicate secrets. |
|
Reference to an older, similar feature request that appeared as a search result (whereas this one here didn't): #6081 |
If I need to rotate my GitHub token or Private Packagist/Artifactory authentication, I would like to do it in one place. NPM supports using environment variables in the
.npmrcfile but I do not see that Composer also supports it in auth.json files. I propose that we add environment variable support so that I could do the following:{ "github-oauth": { "github.com": "${GITHUB_TOKEN}" }, "http-basic": { "packages.mycompany.com": { "username": "first.last@mycompany.com", "password": "${PACKAGIST_MY_COMPANY_PASSWORD}" } } }This would allow me to re-use the same variables across Composer and NPM since we use Artifactory for both at the current project I work at, and I only have to update them in once place (my
.zshenvfile).The text was updated successfully, but these errors were encountered: