❓👂 Question/Feedback - Guidance On Adding Resources That Can be Consumed By Workload Teams

[bzabber]

Question/Feedback

I don't see a pattern in the documentation (perhaps it's not obvious), for how I can add some common fixtures in subscriptions that can be used by Application teams. Ex: Resource Group for a KeyVault, Resource Group for Storage Accounts, Recovery Vaults and so on.

In my case the subscriptions already exist and I see there's an example to accommodate adding the networking and peering.

What would I need to do to extend that a bit to include the resources I mentioned above?

Possible Answers/Solutions?

I'd like to follow a recommended pattern so that it doesn't break away too much from the LZ-Vending approach. (I'd like to reuse, leverage the existing automation as much as possible found in the repo.)