Re: Packaging terraform?
On a different note, I'm guessing that because Go programs encourage libraries to be bundled in, they a pita to package.
Either you break from upstream and compile them dynamically linked, which is a compatibility nightmare. Or you statically compile the package like upstream does, which is a security nightmare (because rather than just security patching the library you need to security patch everything that has that library statically compiled in).
I'm really just guessing though, but the presumption is that debian wouldn't throw up their hands on docker (which btw is kinda a big deal now) without good reason.
On 06/21/2018 01:57 PM, Paul Dejean wrote:
> Because terraform interfaces with proprietary apis usually, it needs to
> be updated more often than stable is updated to be useful.
I have to admit I don't know a lot about proprietary apis. But as for
OpenStack, APIs are quite stable, and (almost?) always backward
compatible thanks to API micro-versions and auto-discoverability. In
fact, I haven't found yet an example of something that broke API
Do we see such breakage often in AWS / Azure / GCE? I'm amazed to read
this, really. How come customers aren't complaining about this then?
Thomas Goirand (zigo)