Hacker Timesnew | past | comments | ask | show | jobs | submitlogin
Terraform 1.6 arrived with breaking changes (github.com/hashicorp)
1 point by nikolay on Oct 6, 2023 | hide | past | favorite | 4 comments


It's a bug from updating the PGP dependency, not a breaking change


Well, for those using Terraform, it's an unannounced breaking change. This shows how poor HashiCorp is testing its minor releases (well, given how long it took to v1, this is more like a major release). They own the registry and could've scanned providers with expired keys, warned developers, and prepared for a smooth release. Instead, they've worked months on something that needed to be tested with popular third-party providers such as the most popular PostgreSQL, MySQL, RabbitMQ, etc. There are hundreds of broken providers. In addition, developers must be notified that keys are about to expire or have expired. There must be an ample red warning on the web UI as well.


Everyone makes these mistakes from time to time and every registry has fallen on its face. They will roll out a fix, it's still not a breaking change, which is something permanent under common parlance. You are using "breaking change" inappropriately


Yup, the correct term would be "broken features".




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: