Utility providers aside (e.g., `null_resource` which for many use cases you can replace with `terraform_data` in versions >= 1.4), I think you’ve missed the poi

Utility providers aside (e.g., `null_resource` which for many use cases you can replace with `terraform_data` in versions >= 1.4), I think you’ve missed the point I was making. Which is: - HashiCorp employees directly maintain an astonishingly small number of those providers. - For the most significant ones (e.g., AWS, Azure) they are working in some form of collaboration with the relevant vendors. - The primary determination on what is broken out into a separate resource or not is based on the API said vendor exposes. - For those major strategic providers I mentioned, they’ve been working to have the providers programmatically generated so it has little to no human intervention and increases the likelihood of day 1 support for any new service or features. Incentives aside, there isn’t opportunity to affect things in the way you’re fearful of. The people with the biggest influence on the design of these things, and whether resources are consolidated or decomposed, work at AWS, Microsoft, Google, etc.