helmfile VS terraform-provider-google

What we’re going to install into the newly created AKS cluster is located in the helm directory. The descriptive Helmfile approach enables us to define applications and their settings in the helmfile.yaml file.

Is there any alternative to https://github.com/roboll/helmfile you are currently using in your company.

Interesting, I have approached this problem using Helmfile (https://github.com/roboll/helmfile) to define a “platform release package.”

To make managing the Helm deployments a little easier I used helmfile (https://github.com/roboll/helmfile).

But in general it's always easier to keep things quite separated. Meaning in separate helm releases. If you want to be able to manage things "together" at will, then you can use helmfile ( https://github.com/roboll/helmfile )

I agree; helm is too declarative.

Whenever I can, I use helmfile[0] for storing variables for helm since it does add a declarative layer on top of helm.

0 - https://github.com/roboll/helmfile

I went through the Helmfile repo Readme to figure out the difference between helmfile sync and helmfile apply. It seems like unlike the apply command, the sync command doesn't do a diff and helm upgrades the hell out of all releases 😃. But from the word sync, you'd expect the command to apply those releases that have been changed. There is also mention of the potential application of helmfile apply to periodically syncing of releases. Why not use helmfile sync for this purpose? Overall, the difference didn't become crystal clear, and I though there could probably be more to it. So, I'm asking.

helmfile is something i’ve used in the past for this https://github.com/roboll/helmfile

I always felt like dependencies in helm are for very simple non-coupled packages. I many times use Helmfile (https://github.com/roboll/helmfile) to manage dependencies instead of banging my head with vanilla Helm.

Once you do that, learn to create dynamic helm charts that use go templating and conditionals: https://github.com/roboll/helmfile

> DNS without CGO works perfectly

It does not. I know this because it impacts my daily work and the work of others. Honestly if you could make my day and go figure out exactly what's going wrong with the pure go DNS implementation it would make my life alot simpler and I wouldn't have to maintain shell scripts that update etc/hosts to hard code in ipv4 addresses for the APIs I access with terraform.

https://github.com/hashicorp/terraform-provider-google/issue...

GCP Terraform Provider

I think the equivalent for AWS is https://registry.terraform.io/providers/hashicorp/aws/latest/docs and for GCP https://registry.terraform.io/providers/hashicorp/google/latest/docs

There's an open issue in the gcp provider for exactly this. I'd recommend thumbs-upping it if you haven't already, as well as subscribing to notifications so you can see when there are updates.

only some people inside google could answer that but here's an issue already? https://github.com/hashicorp/terraform-provider-google/issues/11648

Not sure if you've solved for this or not, but it didn't work for me running terraform as a service account, it appears that it doesn't handle HTTP headers correctly: https://github.com/hashicorp/terraform-provider-google/issues/6738 but it does work with impersonation of that account, which is what I did. Note that your org can only have 1 access policy, and in my case I had to make google_access_context_manager_access_level anyways.

All I can find is an old thread saying cannot do. https://github.com/hashicorp/terraform-provider-google/issues/6413 Has there been any update to this, or does anyone know of a work around?

If you followed that request, you get to this PR which added the feature and updated this documentation