So from a product perspective they basically manage tfstate, you get to use “pre-packaged and recommended” providers (not clear if say aws provider is allowed) and they slapped iam to it? Seems like another one of those frankenstein cloud designs…
Infrastructure Manager: Provision Google Cloud Resources with Terraform
11–20 of 70 posts
Re: Infrastructure Manager: Provision Google Cloud Resources with Terraform
#12Licensing decision aside, I don’t feel a lot of sympathy for Hashicorp here. I think this is different than other scenarios where big MSP’s sell tools based 99% or open source software. This service will largely be used for deployments on Google Cloud, for which Google invests a lot of development effort in maintaining their own provider. It’s not like there’s not already significant contribution from Google to the c…
Why would you assume that there is no license in place for this?
Re: Infrastructure Manager: Provision Google Cloud Resources with Terraform
#13Wonder if they have to pay licensing fees to hashicorp for using terraform this way. It’s essentially replacing terraform cloud for GCP resources.
Which is why it's all the more puzzling Google didn't spring for OpenTF here. They single-handedly could have proven it as the fork of choice but instead they're paying into HashiCorp's bad decision?
Re: Infrastructure Manager: Provision Google Cloud Resources with Terraform
#14So Deployment Manager is finally dead?
Re: Infrastructure Manager: Provision Google Cloud Resources with Terraform
#15I wish AWS would do this and deprecate CloudFormation.
CDK is amazing, you shouldn't be writing cloud formation anymore
Re: Infrastructure Manager: Provision Google Cloud Resources with Terraform
#16So Deployment Manager is finally dead?
It's still in the console, this one is not (yet)
Re: Infrastructure Manager: Provision Google Cloud Resources with Terraform
#17So from a product perspective they basically manage tfstate, you get to use “pre-packaged and recommended” providers (not clear if say aws provider is allowed) and they slapped iam to it? Seems like another one of those frankenstein cloud designs…
This is definitely half baked IMO. Not a whole lot of benefits over running TF with Cloud Build and a storage bucket. Definitely have more control and better UX than the weird hoops you jump through to set this up.
Re: Infrastructure Manager: Provision Google Cloud Resources with Terraform
#18Is there anything particularly painful about working with the Google Cloud Terraform provider? If there isn't, I would rather use OpenTF with that provider and manage state myself.
Re: Infrastructure Manager: Provision Google Cloud Resources with Terraform
#19Licensing decision aside, I don’t feel a lot of sympathy for Hashicorp here. I think this is different than other scenarios where big MSP’s sell tools based 99% or open source software. This service will largely be used for deployments on Google Cloud, for which Google invests a lot of development effort in maintaining their own provider. It’s not like there’s not already significant contribution from Google to the c…
Why would you assume that there is no license in place for this?
They may well do, but to be honest my fundamental point extends beyond just Google. Hashicorp benefits extensively from third parties maintaining their own providers.
Re: Infrastructure Manager: Provision Google Cloud Resources with Terraform
#20I wish AWS would do this and deprecate CloudFormation.
Just use CDK. By far it's the best way to manage AWS infra; AWS also uses it internally.