helmfile VS terraform-provider-azuread

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

There are different Terraform Providers that enable Terraform to interact with Microsoft Azure. The most common one are Azure Stack, AzureDevops, AzureRM, AzAPI and AzureAD.. In this tutorial, we use the AzureRM Terraform Provider. Let's create a Terraform file for the AzureRM Terraform Provider.

It can be for anything. Here is the provider for Azure Active Directory. It looks like it has over a million downloads this week alone so someone is using it..

Since the provider doesnt currently support licensing on [users directly](https://github.com/hashicorp/terraform-provider-azuread/issues/745) i think the only other option is to create a group that maintains specific licenses for user-members... however, that seems to be pay-walled behind Business Premium or azure ad p1

Not officially supported yet: https://github.com/hashicorp/terraform-provider-azuread/issues/68

The support for privileged identity management in Terraform is very limited. One open issue that tracks it is https://github.com/hashicorp/terraform-provider-azuread/issues/547

Source: https://github.com/hashicorp/terraform-provider-azuread/blob/main/internal/services/directoryroles/directory_role_resource.go

I haven't particularly worked with this, but if you're looking for things to see before doing, I would recommend looking at the examples provided by Microsoft: https://docs.microsoft.com/en-us/azure/developer/terraform/ and read through the provider documentation to see the individual pieces: https://registry.terraform.io/providers/hashicorp/azuread/latest/docs