[Jenkins-infra] [?] Should we merge open pull requests into a custom Terraform container?

[Olblak]

It's always a trade off

I usually doesn't like using experimental features (I mean not merged
PR) and especially for production environment.
We have less knowledge than upstream devs about sides effects.
And it may be time consuming to follow improvements until a merge happen
in the upstream project.

In this case we can use an arm template for ACS which I think is fine
for the moment.


-- 
  Olblak

On Fri, Dec 30, 2016, at 12:12 AM, R. Tyler Croy wrote:
> 
> When olblak and I were in the same location, we discussed crafting a
> custom
> Terraform container which we could patch out of the normal Hashicorp
> release
> cycle (see: https://github.com/jenkins-infra/terraform)
> 
> I noticed today when looking for bug fixes that this pull request, which
> adds
> Azure Container Service (ACS) resources exists:
>     https://github.com/hashicorp/terraform/pull/10820
> 
> This might be something that makes olblak's work much easier, so I
> suppose I'm
> asking this question primarily to him: think this is worth merging in and
> creating a jenkinsciinfra/terraform container?
> 
> 
> Cheers
> - R. Tyler Croy
> 
> ------------------------------------------------------
>      Code: <https://github.com/rtyler>
>   Chatter: <https://twitter.com/agentdero>
> 
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> ------------------------------------------------------
> _______________________________________________
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)