News for hackers. Stuff that matters.
Re:Lessons Learned from Writing Over 300k Lines of Infrastru... by yjftsjthsd-h on Monday November 26, 2018 @06:42PM (#18537869)
You are the first person I've encountered who preferred cloudformation over terraform. CF has far worse ability to cope with out-of-band changes or problems in general (in contrast to TF, which can usually just `apply` things back into compliance), and somehow gets feature support slower than TF in spite of being 1st party.
Re:Lessons Learned from Writing Over 300k Lines of Infrastru... by auslander on Monday November 26, 2018 @06:45PM (#18537887)
> just `apply` things back into compliance

If your things are wandering out of compliance by themselves, you have bigger problems, imho.

Re:Lessons Learned from Writing Over 300k Lines of Infrastru... by ucarion on Monday November 26, 2018 @08:29PM (#18538535)
Likely the commenter is referring to development environments, where it is common for infra to be put in bizarre states by actors performing changes. Terraform alone is does not constitute change control.
Re:Lessons Learned from Writing Over 300k Lines of Infrastru... by scarface74 on Monday November 26, 2018 @07:03PM (#18537986)
Then don’t do that. But CF at least now has drift detection

But what I prefer about CF is the “easy button”. If something weird happens or I can’t figure out something, I can use our business support plan with AWS.

Re:Lessons Learned from Writing Over 300k Lines of Infrastru... by yjftsjthsd-h on Monday November 26, 2018 @08:17PM (#18538474)
> drift detection

As of 2 weeks ago[0] drift detection exists, but coverage is poor[1].

[0] https://aws.amazon.com/about-aws/whats-new/2018/11/aws-cloud...

[1] https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui...