💡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!

#
Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

AI isn’t asking questions. It’s just making assumptions.

AI isn’t asking questions. It’s just making assumptions. In consulting or sales, you learn fast: What customers want isn’t always what solves their problem. They ask for solutions they know based on limited knowledge. Experienced consultants do something else: They...

read more

Cancel Culture in IT: How Codes of Conduct Became Weapons

Cancel Culture in IT: How Codes of Conduct Became Weapons Cancel Culture is happening in major communities to developers and contributors, like the: Linux Kernel C++ Standard Committee Python NixOS openSUSE Godot And the reasons? Completely absurd: Being Republican...

read more