I've just vended a subscription with Terraform and none of the providers are registered.
Things as simple as Storage Accounts - why is this happening?
#I've just vended a subscription with Terraform and none of the providers are registered
placid falcon
inner yacht
Not all resource providers are registered by default, including storage.
placid falcon
so you have to do it manually what a pain!
inner yacht
Nah, a lot of them should automatically register the first time you try to provision something from that provider (might not if you're trying via TF). Assuming you have access to register them. It's another form of access control. Need to give TeamA a workspace and need to make sure they don't provision certain things? Disable to providers and make sure they don't have access to register them.
placid falcon
Yeah sigh - i guess. Wouldn't the logical thing be to have "SETS" or to have Default Allow and then deny what you don't want.
That's how AWS do it 🤷♂️
or let me select default allow all ...
cedar pawn
Yeah sigh - i guess. Wouldn't the logical thing be to have "SETS" or to have Def...
That's a decision of the PG, i would suggest to raise a feature request on the github of the involved pg(product group). But i can think of scenarios where there can be good reasons that you don't want hand storage over right away to landing zone. For example if a team is going to migrate highly confidential data, then it would be a good thing to have some extra Governance/Security (Azure Policies&security monitoring) in place, before you enable the resource provider and the team is going to migrate data