{"version":"2.1.242","anchor":"placeholder-credential-values-for-the-gh-aws-and-gcloud-clis","canonical_anchor":"placeholder-credential-values-for-the-gh-aws-and-gcloud-clis","heading":"Placeholder credential values for the gh, AWS and gcloud CLIs","tier":"soon","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/placeholder-credential-values-for-the-gh-aws-and-gcloud-clis","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Placeholder credential values for the gh, AWS and gcloud CLIs\n\nStand-in credential values for gh, AWS and gcloud are defined, with substitution rules unsettled.\n\n**What**\n\nA table now maps each of these command-line tools to the credential environment variables it reads and to stand-in values for them, covering `GH_TOKEN` and `GITHUB_TOKEN`, the full AWS set including container credential URIs, and the Google Cloud SDK token and application default credentials path. A startup step primes these and logs without failing if it cannot. What decides when the placeholders are substituted is not settled by the code that defines them.\n\n**Evidence**\n\n`AWS_CONTAINER_CREDENTIALS_RELATIVE_URI`\n\n- Area: Sandbox\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}