Terraform is currently not reviewing community pull requests

Post by [deleted] » Mon, Sep 06, 2021, 8:45 AM UTC

Post by otterley » Mon, Sep 06, 2021, 9:08 AM UTC

zxcvbn4038 wrote: post #88

devcpp wrote: post #53

Earlier quoted context omitted.

I work at AWS. The service teams do own and write their CloudFormation providers, although if you've written a custom provider you'd see it is somewhat clunky, so it's sometimes considered more of an operational burden, and you can tell. We dogfood both the SDK and CloudFormation internally, we just deal with its numerous gripes much the same way you would externally (although we can also contact service teams direct…

Million dollar question would be if all the “feature requests” that AWS support opens when they don’t know what else to do actually go someplace or if they just get swept aside every few days. I’ve always been under the impression they receive very little or no attention. Even bugs where I have included a reproducible test case that results in an internal error, they just keep trying to close the ticket every few day…

Post by junon » Mon, Sep 06, 2021, 9:13 AM UTC

leetrout wrote: post #6

danpalmer wrote: post #2

These things happen, props to Hashicorp for communicating about it. It would be easy to say that this is a failure of open-source in some way, but to do so would be unfair to the huge amount of work that companies put into tools like this, and the stewardship that they offer, both of which take a lot of time and money. If periods of low activity while teams change are the cost the community needs to pay for that, I t…

I had a conversation with my coworkers when I worked there about being upfront with folks that we wouldn't review or accept their PR and stop leaving people hanging (this was on the TFE provider). I'm glad this was added. I stand by my statement then and now: there is nothing worse than contributing to something open source and then have your PR completely ignored.

Post by takeda » Mon, Sep 06, 2021, 10:08 AM UTC

chousuke wrote: post #67

notatoad wrote: post #36

Earlier quoted context omitted.

heh. i've been considering a switch from ansible to terraform because i've been frustrated by ansible's limited support for some of the edge cases around ALBs. good to hear that terraform also sucks. i'm gradually coming to the conclusion that all the tools that are supposed to make provisioning cloud infrastructure easier aren't as good as a bunch of crappy custom scripts using boto or aws-cli.

Terraform is a massive improvement over Ansible if you do anything non-trivial; even if it sucks, it sucks significantly less than Ansible at managing infrastructure resources. I sometimes fool myself into thinking I can use Ansible in simple cases and that Terraform would be overkill but so far I've regretted those decisions every time.

Post by chousuke » Mon, Sep 06, 2021, 2:58 PM UTC

takeda wrote: post #97

chousuke wrote: post #67

Earlier quoted context omitted.

Terraform is a massive improvement over Ansible if you do anything non-trivial; even if it sucks, it sucks significantly less than Ansible at managing infrastructure resources. I sometimes fool myself into thinking I can use Ansible in simple cases and that Terraform would be overkill but so far I've regretted those decisions every time.

Ansible wasn't designed for IaC, but configuration management, and even at that wasn't the best tool. What made it popular was that it was easiest to start with, but that's pretty much all of its strength compared to the competition.