{"version":"2.1.311","anchor":"managed-settings-commands-keep-projectplugin-env-out-new","canonical_anchor":"managed-settings-commands-keep-projectplugin-env-out-new","heading":"Organization-managed helper commands no longer get repository or plugin env values","tier":"notice","area":"Settings","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/managed-settings-commands-keep-projectplugin-env-out-new","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Organization-managed helper commands no longer get repository or plugin env values\n\nCommands set in managed settings, like `apiKeyHelper`, now run without environment variables from project settings or plugins, except some cloud ones\n\n**What**\n\nAn organization can set commands in managed settings (settings an administrator controls, which you cannot override), such as `apiKeyHelper`, which generates your API credential with your own command. These commands now start without the environment variables supplied by a repository's project settings or by plugins. Environment variables are named values passed to a program when it starts.\n\nA short list of cloud variables still gets through, including `AWS_PROFILE`, `AWS_REGION` and the `CLOUDSDK_*` variables.\n\nIf such a command fails, the error now names the variables that were withheld and says to set them in the `env` of managed settings instead.\n\n**Why**\n\nThis matters to administrators running cloud credential helpers. A value that used to reach the helper from a repository or a plugin now has to be set in managed settings.\n\n- Area: Settings\n- Names: `apiKeyHelper`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}