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

Linter rule suggestion: Flag .bicepparam assignment of secure -> insecure params #16253

Open
anthony-c-martin opened this issue Jan 31, 2025 · 0 comments
Labels

Comments

@anthony-c-martin
Copy link
Member

The following could lead to accidental exposure of secure values in deployment history, because insecureParam has not been marked @secure() yet is being assigned an assumed-secure value.

  • main.bicepparam:
    using 'main.bicep'
    
    param secureParam = 'MYSECRET'
    param insecureParam = secureParam
  • main.bicep:
    @secure()
    param secureParam string
    
    param insecureParam string
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Todo
Development

No branches or pull requests

2 participants