Policy definitions and Policy assignment tries to deploy multiple time in the same scope

[azure]

Policy definitions and Policy assignment tries to deploy multiple time in the same scope

[VitaliZhur]

As a workaround, I have removed these policy assignments for the LandingZone:
modules/archetypes/lib/archetype_definitions/archetype_definition_es_landing_zones.tmpl.json

After that, I was able to deploy successfully (to greenfield env).
And I see that these policy assignments have been created as well. But they have not been deployed. I checked it in state file.

But I still can't find the reason for that...

[J0hn-B]

thank you for your feedback, @VitaliZhur

It looks like you have tried to adjust the configuration in main.tf from within the module.
In this case, deployment failures are expected.

Our suggestion would be to follow the module user guide and examples page for a successful deployment.

This is the minimum default configuration and you can find it here:

# We strongly recommend using the required_providers block to set the
# Azure Provider source and version being used.

terraform {
  required_providers {
    azurerm = {
      source  = "hashicorp/azurerm"
      version = ">= 2.46.1"
    }
  }
}

provider "azurerm" {
  features {}
}

# You can use the azurerm_client_config data resource to dynamically
# extract the current Tenant ID from your connection settings.

data "azurerm_client_config" "current" {}

# Call the caf-enterprise-scale module directly from the Terraform Registry
# pinning to the latest version

module "enterprise_scale" {
  source  = "Azure/caf-enterprise-scale/azurerm"
  version = "0.3.0"

  root_parent_id = data.azurerm_client_config.current.tenant_id
  root_id        = "myorg-1"
  root_name      = "My Organization 1"

}

For more information around the module, please check our wiki.

[VitaliZhur]

Thanks for your answer. I understood my issue, instead of creating a new project with only main.tf to start. I cloned your repo and tried to deploy from there.