2 ms·
I think TF is better at post-setup execution. I haven't used CF in a while, but I remember having it run commands post-setup (outside of user data) being kind o
by nunez 10y ago
I think TF is better at post-setup execution. I haven't used CF in a while, but I remember having it run commands post-setup (outside of user data) being kind of kludgey. I also really really dig its module system; it lets you get incredibly creative. I also heavily prefer HCL over Amazon's DSL (at least what I remember of it when I used it heavily last year. Self referencing security groups were a huge pain in CF but pretty easy in TF)
the biggest win for TF (IMO) is that it doesn't lock you into any provider. It is a lot easier to design TF configs to work in cross-cloud scenarios (well, "easy") than it is to port CF over to something else (which is AWS only.