5 ms·

Looking at the two diagrams shown lower down in the article, I can't be the only one that thinks the "Before" looks infinitely superior to the "After". Yet ano

by ris 8y ago

Looking at the two diagrams shown lower down in the article, I can't be the only one that thinks the "Before" looks infinitely superior to the "After". Yet another third party service to depend on which has unknown reliability or future business model plans.

ronjouch 8y ago
Yes! To me, that sounds similar (or one step further) to dev/ops folks exclaiming "Docker!" at the mildest trouble with builds / CI / isolation. After spending time with Docker, I like it when it's deserved, but my first reaction is one of "Uh, it's one more layer, it will bring new tooling and required knowledge and error conditions, let's only do it if we have to".
reptation 8y ago
Yeah, this appears to be accomplishing the same purpose as the 'Terragrunt' wrapper which uses DynamoDB for locking state IIRC https://github.com/gruntwork-io/terragrunt https://github.com/gruntwork-io/terragrunt
- jen20 8y ago
  If using the S3 remote state backend, Terraform itself has supported this with no wrapper for quite some time now.
  - kitotik 8y ago
    Doesn’t the consul backend support this as well?
    - jen20 8y ago
      Several do - I'm not sure which offhand though. The docs for each backend (e.g. [1]) explain what is supported. [1]: https://www.terraform.io/docs/backends/types/azurerm.html https://www.terraform.io/docs/backends/types/azurerm.html
tjbiddle 8y ago
While I understand where you're coming from, I can tell you're not a user of Terraform. As someone who uses Terraform daily, and has brought it to nearly a dozen other teams at my employer - these new announcements are pretty cool :-) Including the announcement about a free tier for Terraform Enterprise (Which, mind you - is optional, they are not forcing you to go through it)
- ris 8y ago
  Thanks, man - but I am a terraform user. We use the S3 backend for state management and it works really well for us. The thing that I like most about terraform is that ultimately, it's just a tool. Just something independent and (mostly) pinnable & controllable that runs on peoples' machines. > Which, mind you - is optional Everything starts out as optional before they start ramping up the monetization model. But of course, it's an open source project, so wherever Hashicorp want to take this, the community can just fork it. However, it's clear where the center of gravity for future development is going to be - towards pushing Hashicorp into your critical path.

by ris 8y ago

ronjouch 8y ago

Yes! To me, that sounds similar (or one step further) to dev/ops folks exclaiming "Docker!" at the mildest trouble with builds / CI / isolation. After spending time with Docker, I like it when it's deserved, but my first reaction is one of "Uh, it's one more layer, it will bring new tooling and required knowledge and error conditions, let's only do it if we have to".

reptation 8y ago

Yeah, this appears to be accomplishing the same purpose as the 'Terragrunt' wrapper which uses DynamoDB for locking state IIRC https://github.com/gruntwork-io/terragrunt https://github.com/gruntwork-io/terragrunt

jen20 8y ago
If using the S3 remote state backend, Terraform itself has supported this with no wrapper for quite some time now.
- kitotik 8y ago
  Doesn’t the consul backend support this as well?
  - jen20 8y ago
    Several do - I'm not sure which offhand though. The docs for each backend (e.g. [1]) explain what is supported. [1]: https://www.terraform.io/docs/backends/types/azurerm.html https://www.terraform.io/docs/backends/types/azurerm.html

tjbiddle 8y ago

While I understand where you're coming from, I can tell you're not a user of Terraform. As someone who uses Terraform daily, and has brought it to nearly a dozen other teams at my employer - these new announcements are pretty cool :-) Including the announcement about a free tier for Terraform Enterprise (Which, mind you - is optional, they are not forcing you to go through it)

ris 8y ago
Thanks, man - but I am a terraform user. We use the S3 backend for state management and it works really well for us. The thing that I like most about terraform is that ultimately, it's just a tool. Just something independent and (mostly) pinnable & controllable that runs on peoples' machines. > Which, mind you - is optional Everything starts out as optional before they start ramping up the monetization model. But of course, it's an open source project, so wherever Hashicorp want to take this, the community can just fork it. However, it's clear where the center of gravity for future development is going to be - towards pushing Hashicorp into your critical path.