[jhugo]

Thanks for the downvote and the no-content comment, I guess? I've worked with numerous large Terraform configurations, and the ones that use terraform-aws-modules are harder to maintan, have more churn due to updates of the modules, and are more divorced from the actual underlying cloud resources due to random decisions made by the module authors.

I really struggle to understand the reason for using the modules rather than the underlying resources, except that there are a lot of tutorials and blog posts written based on using the modules.

Maybe you can enlighten me rather than writing a three-letter comment?

[nrmitchi]

I will enlighten you.

> serve very little purpose other than to add a dependency and create problems

You're expressing your opinion as fact in a way that only serves to degrade people who don't agree with you.

Obviously these modules serve a purpose, otherwise the repositories would not have hundreds-to-thousands of github stars/forks, and people would not be arguing about a license change on the front page of HN.

[jhugo]

> Obviously these modules serve a purpose, otherwise the repositories would not have hundreds-to-thousands of github stars/forks, and people would not be arguing about a license change on the front page of HN.

Have you worked with the modules in question? If you have, please enlighten me to the obvious purpose that they serve. As I pointed out, I've worked with them extensively, and worked on comparable configurations that avoid them, and they create many problems (the wrappers introduce their own churn due to version updates, and often have mistakes in their interpretation of the underlying resources, etc) while solving virtually none. Several orgs I've worked for actually ban these and similar external modules due to these problems.

It's telling that the only substantive reply I received merely points out the number of stars rather than actually explaining why people should use these wrappers.

[antonbabenko]

no