Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add env variable to warn customers #374

Merged
merged 2 commits into from
Jan 31, 2024
Merged

Add env variable to warn customers #374

merged 2 commits into from
Jan 31, 2024

Conversation

darrentu
Copy link
Contributor

Show warning to customer if secret will get revealed. This is for the Az CLI and Az Powershell commands.

Copy link

Image size with this change is base: 5810MB, tools: 8442MB.

@darrentu darrentu changed the title Update tools.Dockerfile Add env variable to warn customers Jan 23, 2024
linux/tools.Dockerfile Outdated Show resolved Hide resolved
@@ -71,5 +71,7 @@ RUN ln -s /usr/bin/node /usr/bin/nodejs
# Add dotnet tools to PATH so users can install a tool using dotnet tools and can execute that command from any directory
ENV PATH ~/.local/bin:~/bin:~/.dotnet/tools:$PATH

ENV AZURE_CORE_SHOW_SECRETS_WARNING True
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AZURE_CORE_SHOW_SECRETS_WARNING is Azure CLI specific, mapped from az config set core.show_secrets_warning.

As shown in Azure/azure-cli#10241, there are already some common environment variables, such as AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_SUBSCRIPTION_ID.

If Azure CLI and Azure PowerShell want to share the same env var, it's better to create a common env var such as AZURE_SHOW_SECRETS_WARNING.

Co-authored-by: Yishi Wang <yishiwang@microsoft.com>
Copy link

Image size with this change is base: 5818MB, tools: 8464MB.

@darrentu darrentu merged commit e56ebe9 into master Jan 31, 2024
2 checks passed
@darrentu darrentu deleted the env_show_warning branch July 25, 2024 21:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants