Pulumi – Modern Infrastructure as Code

Re:Pulumi – Modern Infrastructure as Code by rainforest on Tuesday April 14, 2020 @12:17PM (#22867789)

One use case that TF really frustrates me with is anything conditional: if I want to do blue/green the best I can do is duplicate the entire infrastructure and wrap my terraform invocations with some brittle script that repeatedly runs TF with various targets. The script only allows me to define the target state, but it is quite common that I care how that final state is reached.

Create-if-not-exists is also really poor in TF (probably by design), if you want to reuse your TF configs for different environments in the same account, you either have to ensure everything won't collide name-wise, or split your TF into immutable infrastructure and really-immutable infrastructure.

[ Parent | on HN ]

Re:Pulumi – Modern Infrastructure as Code by rjzzleep on Tuesday April 14, 2020 @12:40PM (#22868108)

Doesn't terragrunt allow you to do that?

The looping code while better with terraform 0.12 is still quite nasty though.

https://terragrunt.gruntwork.io/docs/getting-started/quick-s...

[ Parent | on HN ]

Re:Pulumi – Modern Infrastructure as Code by core-questions on Tuesday April 14, 2020 @02:50PM (#22869907)

The idea of having to use a 3rd party tool to generate config for my 3rd party tool that generates config just seems Wrong.

At this point I'd rather write idiomatic but repetitive Terraform and know that I will be safer on upgrades, as long as I continue to refactor and clean up my modules for the new functionality Hashi is releasing.

[ Parent | on HN ]

Re:Pulumi – Modern Infrastructure as Code by rainforest on Tuesday April 14, 2020 @01:26PM (#22868753)

I wasn't aware of this, looks like it would solve some of our pain points, thanks!

I think the existence of tools like this is a succinct way to say that static/declarative languages are really hard to execute.

[ Parent | on HN ]