[email protected]

Patch Changes

• 329fd82: Added support to aws provider version 6

[email protected]

Patch Changes

• 2db0a80: Fix InvalidDefaultArgInFrom error on docker build

[email protected]

Minor Changes

• 0d8e640: Added examples before / after DX in blog post

[email protected]

Major Changes

• 6b2d5bc: # Major Changes

  1. Replace the tier variable with a new use_case variable for tiering configuration.
  2. Add new variables size for sku override.
  3. Added README documentation.

  Upgrade Notes

  Old Value	New Value	Description
  s	none	Does not exist anymore
  m	none	Does not exist anymore
  l	default	Ideal for production environments
  xl	high_load	Ideal for high_load scenarios
  xxl	none	Does not exist anymore

  This change simplifies and clarifies the selection of Function App Exposed.

  To migrate to this new major version:

  1. Update the module version to ~> 2.0 in your Terraform configuration.
  2. Update your module configuration to use the new use_case variable instead of tier.
  3. Optionally, configure the new size variable to create the desired SKU within the Function App Exposed.

  For Example:

  • Before

    module "function_app_exposed" {
      source  = "pagopa-dx/azure-function-app-exposed/azurerm"
      version = "~> 1.0"
      tier    = "l"
      # ...other variables...
    }

  • After

    module "function_app_exposed" {
      source  = "pagopa-dx/azure-function-app-exposed/azurerm"
      version = "~> 2.0"
      use_case = "default"
      # ...other variables remain unchanged...
    }

[email protected]

Major Changes

• 06c22a0: # Major Changes

  1. Replace the tier variable with a new use_case variable for tiering configuration.
  2. Add new variables size for sku override.
  3. Added README documentation.

  Upgrade Notes

  Old Value	New Value	Description
  s	none	Does not exist anymore
  m	none	Does not exist anymore
  l	default	Ideal for production environments
  xl	high_load	Ideal for high_load scenarios
  xxl	none	Does not exist anymore

  This change simplifies and clarifies the selection of Function App.

  To migrate to this new major version:

  1. Update the module version to ~> 4.0 in your Terraform configuration.
  2. Update your module configuration to use the new use_case variable instead of tier.
  3. Optionally, configure the new size variable to create the desired SKU within the Function App.

  For Example:

  • Before

    module "function_app" {
      source  = "pagopa-dx/azure-function-app/azurerm"
      version = "~> 3.0"
      tier    = "l"
      # ...other variables...
    }

  • After

    module "function_app" {
      source  = "pagopa-dx/azure-function-app/azurerm"
      version = "~> 4.0"
      use_case = "default"
      # ...other variables remain unchanged...
    }

[email protected]

Major Changes

• fe1260b: # Major Changes

  1. Replace the tier variable with a new use_case variable for tiering configuration.
  2. Add new variables size for sku override.

  Upgrade Notes

  Old Value	New Value	Description
  xs	none	Does not exist anymore
  s	none	Does not exist anymore
  m	none	Does not exist anymore
  l	default	Ideal for production environments
  xl	high_load	Ideal for high_load scenarios

  This change simplifies and clarifies the selection of App Service exposed.

  To migrate to this new major version:

  1. Update the module version to ~> 2.0 in your Terraform configuration.
  2. Update your module configuration to use the new use_case variable instead of tier.
  3. Optionally, configure the new size variable to create the desired SKU within the App Service.

  For Example:

  • Before

    module "app_service" {
      source  = "pagopa-dx/azure-app-service-exposed/azurerm"
      version = "~> 1.0"
      tier    = "l"
      # ...other variables...
    }

  • After

    module "app_service" {
      source  = "pagopa-dx/azure-app-service-exposed/azurerm"
      version = "~> 2.0"
      use_case = "default"
      # ...other variables remain unchanged...
    }

[email protected]

Major Changes

• e607688: # Major Changes

  1. Replace the tier variable with a new use_case variable for tiering configuration.
  2. Add new variables size for sku override.

  Upgrade Notes

  Old Value	New Value	Description
  s	none	Does not exist anymore
  m	none	Does not exist anymore
  l	default	Ideal for production environments
  xl	high_load	Ideal for high_load scenarios

  This change simplifies and clarifies the selection of App Service.

  To migrate to this new major version:

  1. Update the module version to ~> 2.0 in your Terraform configuration.
  2. Update your module configuration to use the new use_case variable instead of tier.
  3. Optionally, configure the new size variable to create the desired SKU within the App Service.

  For Example:

  • Before

    module "app_service" {
      source  = "pagopa-dx/azure-app-service/azurerm"
      version = "~> 1.0"
      tier    = "l"
      # ...other variables...
    }

  • After

    module "app_service" {
      source  = "pagopa-dx/azure-app-service/azurerm"
      version = "~> 2.0"
      use_case = "default"
      # ...other variables remain unchanged...
    }

@pagopa/[email protected]

Patch Changes

• b5b6400: First release of the DX MCP Server. In this first version, the MCP server exposes the "QueryPagoPADXDocumentation" tool that queries an Amazon Bedrock Knowledge Base containing the DX documentation website.

[email protected]

Patch Changes

• c293615: First release of the GitHub Action: runs terraform plan, masks sensitive values, and removes unnecessary lines to reduce the final output size.

[email protected]

Minor Changes

• 6decc69: # Minor Changes

  Disabled local authentication in the Azure Cosmos DB account module by setting local_authentication_disabled = true

  Upgrade Notes

  This is a breaking change that affects how authentication works with Cosmos DB:

  • Users must now configure the new authorized_teams variable with principal IDs of teams that need reader or writer access (See PR: #549).

    Without this configuration, teams will no longer be able to manage databases through the Azure portal

  • Connected applications (function app/app services) also require appropriate role assignments to continue functioning correctly.

    For Example:

    module "example_cosmos" {
      source  = "pagopa-dx/azure-cosmos-account/azurerm"
      version = "~> 0.0"
      # other variables
    }
    
    module "example_app_service" {
      source  = "pagopa-dx/azure-app-service/azurerm"
      version = "~> 2.0"
      # other variables
    }
    
    module "app_service_roles" {
      source  = "pagopa-dx/azure-role-assignments/azurerm"
      version = "~> 1.0"
      principal_id    = module.example_app_service.app_service.app_service.principal_id
      subscription_id = data.azurerm_subscription.current.subscription_id
      cosmos = [
        {
          account_name        = module.example_cosmos.name
          resource_group_name = var.resource_group_name
          description         = "Grants write access to CosmosDB for the App Service"
          role                = "writer" # other possible values: "reader" e "owner"
      }]
    }