[Jenkins-infra] Request for feedback: IEP-003 - Terraform for describing infrastructure as code

R. Tyler Croy tyler at monkeypox.org
Fri Nov 18 01:04:55 UTC 2016

Following the IEP process[0], I would like feedback on this design document for
another integral part of bootstrapping project infrastructure on Azure. In this
proposal I posit that all infrastructure resources on Azure should be defined
via Terraform:


Whereas IEP-002 suggests a network topology, IEP-003 allows me/you/whoever to
actually define that network topology in code which can then be executed to
*do it.*

We have not had a consistent API for provisioning resources in the past, so I'm
quite enthusiastic about defining our infrastructure in a way that reduces
mouse clicks or support tickets :)

[0] https://github.com/jenkins-infra/iep/tree/master/iep-001

- R. Tyler Croy

     Code: <https://github.com/rtyler>
  Chatter: <https://twitter.com/agentdero>

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20161117/dcb1aa93/attachment.asc>

More information about the Jenkins-infra mailing list