2 ms·
This is a bug we just hit 5 minutes ago on 0.6: One of our CD builds failed because of a configuration issue - a variable wasn't properly set, leading terraform
by scrollaway 10y ago
This is a bug we just hit 5 minutes ago on 0.6: One of our CD builds failed because of a configuration issue - a variable wasn't properly set, leading terraform to continuously ask jenkins' stdin for a password.
We fixed the bug. But somehow, that previous build wiped the state file. When we pushed the fix, terraform freaked out and started deleting all our instances, including S3 redirects that weren't managed by it which we explicitly told it to ignore.
That sucked.
- irq 10y agoAlways, always view (and save to disk) tf's plan. And if it looks good, apply the saved plan output.
- scrollaway 10y agoDid view it... locally. It kind of defeats the point if it's not reliable enough to trust it'll behave the same from a different machine. No harm done, we're still in beta to catch bugs exactly like those, but our initial enthusiasm with terraform has been waning very quickly. Like I said, I love the design, but it's just not there yet.
- hedwall 10y agoDo you keep a state file per environment or do you have one big state file for all your environments?
- jen20 10y agoI would consider this a bug - if you can open an issue on the https://github.com/hashicorp/terraform https://github.com/hashicorp/terraform repository, we will look into it prior to 0.7.1.