A dotnet global tool for extracting settings from Azure App Configuration Service and stashing them as User Secrets.
Use the following command to install the .NET Global Tool:
dotnet tool install --global AzAppConfigToUserSecrets.Cli
To invoke the tool you need to use the name actus (AppConfigToUserSecrets)
You can uninstall the tool with the following command:
dotnet tool uninstall --global AzAppConfigToUserSecrets.Cli
actus export --tenant-id <TENANT-ID> --user-secrets-id <USER-SECRETS-ID> --endpoint "https://<YOURAPP>.azconfig.io"
This will spawn an interactive authentication flow.
You can configure your application to use User Secrets by right clicking on the project in Visual Studio 2022 Solution Explorer and selecting the "Manage User Secrets" option from the context menu.
User Secrets are stored in %APPDATA%\Microsoft\UserSecrets\<user_secrets_id>\secrets.json on Windows and ~/.microsoft/usersecrets/<user_secrets_id>/secrets.json on Linux/macOS.
Note: User Secrets does not encrypt the stored secrets and shouldn't be treated as a trusted store. They are stored in plain text in one of the above locations.
AzAppConfigToUserSecrets is available under the Apache 2.0 open source license.
For any licensing questions, please email [email protected]
This project is sponsored by endjin, a UK based Microsoft Gold Partner for Cloud Platform, Data Platform, Data Analytics, DevOps, and a Power BI Partner.
For more information about our products and services, or for commercial support of this project, please contact us.
We produce two free weekly newsletters; Azure Weekly for all things about the Microsoft Azure Platform, and Power BI Weekly.
Keep up with everything that's going on at endjin via our blog, follow us on Twitter, or LinkedIn.
Our other Open Source projects can be found on GitHub
This project has adopted a code of conduct adapted from the Contributor Covenant to clarify expected behavior in our community. This code of conduct has been adopted by many other projects. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.