Azure / Azure/azure-functions-core-tools
Consider removing/masking account keys from logs when deploying Azure Functions for the first time
- Dominant language
- C#
- Stars
- 1.5k
- Forks
- 498
- Avg merge
- 5d 4h
- Merged PRs (30d)
- 15
Description
### Version
Latest
### Description
Hello,
When deploying an Azure Function from local to the cloud, the internally-used Storage Account Key is showed multiple times on the screen in plaintext.
Please consider masking these secrets in the deployment logs and terminal output.
Originally reported [here](https://github.com/microsoft/Oryx/issues/2476)
Thank you
### Steps to reproduce
Deploy an Azure Function (Python runtime) in VS Code using `func init`, then `func new` then `func azure functionapp publish`.
Contributor guide
Research direction
Reproduce the issue with `func init`, `func new`, and `func azure functionapp publish` for a Python Azure Function, then trace where deployment logs and terminal output are produced. Done means the storage account key and other secrets are masked in those outputs, with the first-deployment scenario covered by regression testing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- cli, cloud, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100