You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SettingsArea: what it touches
ImprovementsKind: in v2.1.311,
ImprovementsSection of the release
What
An 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.
A short list of cloud variables still gets through, including AWS_PROFILE, AWS_REGION and the CLOUDSDK_* variables.
If 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.
Why
This 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.
