The "everything with Terraform" pattern #172
roberthstrand
started this conversation in
Platforms
Replies: 1 comment
-
Managing infrastructure well, at enterprise scale is not generally going to lie with each development team. It's certainly possible, but the assumption that each team can deliver app and infra code, and deliver at a high level, means that we're imposing quite a bit on those teams. Would love to discuss. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Like I mentioned in the last WG meeting, I would like to do an example of a pattern using only one tool for both app delivery and infra delivery. My daily driver / tool of trade / reason why I get payed is Terraform, so this is a very natural outlet for me. I did, and kinda still do, have a concern about the scope of this pattern and how to present it properly.
This directly ties into #167, and how to structure patterns.
My idea is to create an example of deploying podtato-head, to Kubernetes, and have Terraform do both the infrastructure and application deployment. I could do a simple flat structure, but at that point I don't feel that the example would show off the benefits of this approach. I would rather show how I would set this up in production, rather than the bare minimum for it to work.
For a holistic and flexible deployment with Terraform, the code structure would look something like this:
This is a bit more than what some of the examples usually show, which is why I suggested in the meeting that we could create a repository for patterns of this size under the podtato-head organization and then keep the documentation for it in the tag-app-delivery repository under the directory
cooperative-delivery-wg/patterns/terraform
.I will also contribute a simple delivery example using Terraform for podtato-head as well, this would be much more static and straight forward and can live with the other deployment examples.
Any thoughts, ideas, or feedback to this approach? Am I overthinking about this, does anyone else think that all of this could easily live in the patterns folder and not it's own repository?
cc: @joshgav @thschue
Beta Was this translation helpful? Give feedback.
All reactions