On Thu, Jun 21, 2018 at 04:30:38PM -0400, Noah Meyerhans wrote:
> Consider the terraform AWS provider:
> https://github.com/terraform-providers/terraform-provider-aws/releases
> It has a release on a weekly basis. GCE and Azure are bi-weekly:
>
>From my experience it's much healthier for the stability of your infra to
gradually update the version of ansible you're using to manage it, rather
than trying to use a dramatically new version of ansible infrequently. Just
because there's less room for error in small compatibility changes your
Hi,
On 18-06-21 07:06:35, Paul Dejean wrote:
> Oh I'd also like to add, for a practical example of such a noob trap,
> see the ansible package (which I wouldn't recommend using).
Could you please elaborate on that?
Cheers,
Georg
signature.asc
Description: Digital signature
I'll echo what Noah said. Backwards compatibility is maintained but new
features and API's are constantly evolving and being added. The issue with
any Cloud platform is that all API clients need to be updated frequently in
order to maintain state with the current platform. Things like Terraform
On Thu, Jun 21, 2018 at 10:03:32PM +0200, Thomas Goirand wrote:
> 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
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
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?)
Oh I'd also like to add, for a practical example of such a noob trap, see
the ansible package (which I wouldn't recommend using).
Stability is mainly useful on software that you run on production, rather
than software you use for setting up production. So for instance I'd love
for a docker
Because terraform interfaces with proprietary apis usually, it needs to be
updated more often than stable is updated to be useful.
So while it may (or may not, i dunno all the details) be technically
allowed and possible. A terraform package in stable would be something of a
noob trap.
On Thu,
On Thu, Jun 21, 2018 at 09:45:27AM +0200, Thomas Goirand wrote:
> Has any of you ever tried terraform, and would it be worth packaging?
> Should this go in the cloud team as well? Any volunteer?
You mean: Terraform and the providers? I don't think you want to open
that pit.
Bastian
--
Without
Hi,
Has any of you ever tried terraform, and would it be worth packaging?
Should this go in the cloud team as well? Any volunteer?
Cheers,
Thomas Goirand (zigo)
11 matches
Mail list logo
