terraform forces you to write custom providers instead of letting you glue tools together. cloudformation has the same issue with custom resources, though the

terraform forces you to write custom providers instead of letting you glue tools together. cloudformation has the same issue with custom resources, though the abstraction is better since you can write custom resources in whatever language you want. neither of them solve for CI or pull request workflows themselves, so people try to bridge the gap with Jenkins and now the frankenstein monster comes to life -- now you've got golang, groovy, yaml, none of which your product devs generally have any familiarity with, let alone the idiosyncrasies of terraform state management, cloudformation stacks stuck in ROLLBACK_COMPLETE, yaml whitespace sensitivity, Jenkins scripting sandbox woes, troubleshooting from logs without being able to step through a debugger in an IDE, errors that only happen in eu-west-3, etc, etc... Clutch looks great!