💡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

SpecFlow: Great concept, flawed execution.

SpecFlow: Great concept, flawed execution. SpecFlow, a BDD framework designed to make writing scenarios a breeze for requirement analysts. The problem: It falls short of its promise. ❌ The reality? Analysts rarely, if ever, write the specs themselves. Instead,...

read more

What if…? Production has a Staging slot.

What if...? Production has a Staging slot. Staging or QA environment needs to be the same or as close to production as it can be. Preferably, you want to restore a recent backup 💾 from Production as Staging and then deploy your changes 🔄. Kudos 👏 if you've fully...

read more

UUID v7 coming in .NET 9

UUID v7 coming in .NET 9 For those that didn't know, you can create Guids in different ways (algorithms). System.Guid supports UUID v4 out-of-the-box, the most used version. UUID v7 is now added, which creates Guids based on the current time. This means Guids can be...

read more