Open gsuttie opened 2 years ago
Thanks for adding this @gsuttie
I've forwarded this and the related twitter discussion to teams that are involved in these areas. I'll report back here once folks have discussed and we have a plan to share.
These are great examples that we need to cover.
I have one other idea if that's ok.
The Azure DevOps Twitter account calls out 4 or 5 great community posts each week which is very cool - could we perhaps just add those links/blog posts to a Github community page for Azure DevOps and link that from the docs - and then do that across more and more of the areas like .net, bicep, etc.
Scenarios pages for how to do things that the community has blogged about - we give them a little bit of kudos and share it via twitter maybe and this will take off. I know the Azure DevOps calling people out for good community content is really nice and very much appreciated.
This is what I am thinking about with regards to me working with customers and them asking for what I am about to try to describe - I have also run into this numerous times. Let's make a scenario.
Scenario:- Jane needs to integrate Azure Key Vault into her code to be able to store and retrieve secrets, she also needs to use KeyVault to store the connection strings to Azure Service Bus. Consider caching
Things to consider:- What is the code sample for doing this in .Net Framework and .Net Core? Should she be using Role Based Access Control or access policies within Key Vault? System Assigned Managed Identity or User assigned - what does Microsoft recommend and why? Can she cache the Key Vault calls or is it ok to look up secrets each time ? What would be the recommended way to cache these calls? How do I connect from my code locally, If I cant use Managed Identity locally do I need a ClientId / Client Secret combination, where do I store that - i.e. do I check it in or use User Secrets?
Ways to Implement:- So this is now more like a real-world scenario where people are making mistakes about how to use Key Vault in code, I've seen numerous customers struggle with these types of scenarios.
Project Based learning:- Tailwind traders was a project sample that many people could download and learn from, I personally think this is the way to go. It's not easy its not straightforward but a lot of the scenarios are used again and again and maybe we could vote on scenarios we would like to see.
I understand this is difficult - but I see customers say I know how to create this azure service but I have no real clue how to glue a system together.