[ramish94]

Terraform (as you may well have already found out) is a blessing and a curse. It's great for instantiating infrastructure quickly and repeatedly, but what it's not great for is managing it going forward and streaming changes (it seems to break A LOT when there is drift from managed infrastructure vs. real life infrastructure).

Do you guys plan to handle managing instances created via terraform code via Gallery, or is it strictly a tool to instantiate environments and add triggers around it?

Like I'm thinking of cases where you might want to edit your existing env created by Gallery with other stuff that other teams may have worked on and merged onto prod. If I edit the config, there could be a lot breaking changes

[jag729]

Absolutely - managing and syncing the state of IaC tools is core to the value of Gallery. Infrastructure templates can be edited without changing currently-active environments, and this is handled gracefully right now. Propagating template updates to running environments seamlessly is also on our roadmap.

[ramish94]

Thanks for the reply. It certainly will be an interesting technical challenge to try and propagate changes efficiently. Speaking from experience (I've worked with Terraform a lot the past 2 years), it can be a tough nut to crack, so good luck!

I would add one more thing (and this is maybe for down the line): There's a use case for duplicating envs beyond just development environments. There's a lot of value in cases where the SaaS product itself requires on-demand environment generation. Where customers of it need staging instances so they can see what config changes are before they merge to production. Obviously in that case, you're treating an actual product like a terraform provider, and the API's of that product as resources. I would explore that down the line because there's a lot of value in a service like that.

FYI, I would love to get involved any way I can to help you guys grow this. Let me know how I can help! mailto:[e-mail] if you're interested :)