I’ve kind of considered something similar to this approach but ended up using a graphdb to keep dependencies instead. Using a db gives you a better way of modi

I’ve kind of considered something similar to this approach but ended up using a graphdb to keep dependencies instead. Using a db gives you a better way of modifying meta data in batches which might be required at scale. It also makes it possible for tooling to query stuff quickly and do operations such as setting consul intentions, register something in an api gateway or other surrounding config tasks. The pipelines we built checked out complete subgraphs from an api and generated json that referenced versioned TF modules and committed these to a service repo. Thought about open-sourcing for a long time but never could get the go from legal. :( This is very cool though!