2 ms·
Sounds like a plan for a next generation cloud provider. They all have internal state about your account and what's running there; they just don't really expose
by jillesvangurp 4y ago
Sounds like a plan for a next generation cloud provider. They all have internal state about your account and what's running there; they just don't really expose it in a standardized way. Nor do they provide standardized ways to update that (other than a lot of cli tools and REST APIs).
We keep coming up with these layers of abstractions around stuff that at the bottom is essentially already stateful but just not in a useful way. Doing it right from the ground up might help. Of course, left to the usual suspects, this would just turn into another Frankenstein blackhole of devops time. The usual suspects are billion dollar corporations that thrive on layers of complexity.
- InvaderFizz 4y agoOracle Cloud does this. You can export Terraform for a Compartment[0] (think LDAP OU). This is how we do our initial terraform for new projects. We build up what is missing by hand, then export the terraform to save time and effort in building our own internal templates. We throw away most of it, but it is very useful for not having to look up how every aspect is named and what options are needed. 0: https://docs.public.oneportal.content.oci.oraclecloud.com/en-us/iaas/developer-tutorials/tutorials/tf-resource-discovery-setup/01-summary.htm https://docs.public.oneportal.content.oci.oraclecloud.com/en...