💡Tip: Why not use dotnet user-secrets for local dev team?

by Dec 1, 2023

💡Tip: Why not use dotnet user-secrets for local dev team?

The question arises often, but it’s not team-friendly in an active codebase.

Why?

  • When secrets are added or altered, everyone must be informed of new keys/values.

  • Onboarding means transferring user secrets machine to machine.

The solution? Azure Key Vault for local development.

  • It informs the entire team when a secret is added/changed.

  • Onboarding is simply adding the new member to the Azure Active Directory Group with Azure Key Vault access.

Problem solved!

#

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Scrum conceals bad teams.

Scrum conceals bad teams. Far too often, we confuse Scrum with a magic wand that transforms any team into a high-performing 'dream team'. It's tempting to believe that the sprint system, with its regular completion and initiation of tasks, gives us an agile and...

read more

🚀 Process Automations in Microsoft Loop!

🚀 Process Automations in Microsoft Loop! Now you can create Power Automate-backed rules to streamline repetitive tasks in your Loop table. See https://insider.microsoft365.com/en-us/blog/streamline-your-workflow-with-automation-in-microsoft-loop Loop is slowly...

read more

You don’t control the truth in Production!

You don't control the truth in Production! Now a days multiple teams/projects are working on the same Dataverse production environment. So thinking you can manage the complete production truth in your ALM pipeline is strange. Not every environment is 💯 equal to...

read more
Share This