Handling Local Secrets with PowerShell: Using $env and Windows Environment Variables
Managing sensitive information such as API keys, access tokens, and database credentials, is a crucial aspect of software development. Ensuring that these secrets are not exposed or compromised is of utmost importance, as it can lead to security brea...
charlesw.hashnode.dev2 min read
Guy Leech
Chief PowerShell Officer
Agreed to no hard coded secrets, disagree with storing them in clear text in environment variables unless they are stored encrypted. I have things like Azure tenant and subscription id in environment variables for ease of passing to scripts but no passwords other than some stored using SecureStrings in clixml files which are populated by code in my PS profile