![]() |
Liam Bennett |
| @liamjbennett | |
@stack72 I would consider it now for sure. As long as the jobs dir is on separate EBS then why not.
![]() |
Liam Bennett |
| @liamjbennett | |
@stack72 I would consider it now for sure. As long as the jobs dir is on separate EBS then why not.
![]() |
Liam Bennett |
| @liamjbennett | |
@webandphp @jaxdevops yeah I’ve already done this now. No need to keep tweeting it.
![]() |
Liam Bennett |
| @liamjbennett | |
@stack72 I’d be interested in knowing more about why you’d use terraform at the provisioning layer.
![]() |
Liam Bennett |
| @liamjbennett | |
@stack72 would you not just use something like puppet apply or ansible? They already have big communities of code to reuse.
![]() |
Liam Bennett |
| @liamjbennett | |
@stack72 it might be a little easier if the cfgmgmt tools had core provisioners (like the chef client one) to make this story better.
![]() |
Liam Bennett |
| @liamjbennett | |
@swade1987 @stack72 that is the pattern I have seen used so far but I don’t like the thought of having that many AMI builds for each role.
![]() |
Liam Bennett |
| @liamjbennett | |
Reminded that more puppet modules need to support passing custom templates so that consul-template can be used instead.
![]() |
Liam Bennett |
| @liamjbennett | |
@stack72 @swade1987 how often do you change anything in your base ami?
![]() |
Liam Bennett |
| @liamjbennett | |
@stack72 so are you saying you’d prefer to use TF modules rather than packer+puppet+TF?
![]() |
Liam Bennett |
| @liamjbennett | |
@stack72 so what specifically would you need a rundeck TF module for?