[email protected]

Patch Changes

• 1841454: Include input sku_size in Azure Static Web Apps HCL snippet
• 8ea5b13: Enabled llms.txt generation

[email protected]

Patch Changes

• bc9645d: Fix terraform test with new Storage Account module version

@pagopa/[email protected]

Minor Changes

• eefc4d3: Add use-pnpm codemod to migrate a project from yarn to pnpm
• eefc4d3: Add update-code-review codemod to update the js_code_review workflow to the latest version
• eefc4d3: Add use-azure-appsvc codemod to migrate legacy deployment workflows

[email protected]

Patch Changes

• 707b5cf: Document AWS to Azure VPN module

[email protected]

Major Changes

• 6e12973: # Major Changes

  1. Replace the tier variable with a new use_case variable for tiering configuration.
  2. Add new variables for container, queue and tables creation.

  Upgrade Notes

  Old Value	New Value	Description
  s	development	Used only for development and testing purposes
  l	default	Ideal for production environments
  none	audit	For storing audit logs with high security and long-term retention
  none	delegated_access	For sharing files externally, forcing secure access patterns
  none	archive	For long-term, low-cost backup and data archiving

  This change simplifies and clarifies the selection of Storage Account.

  • The audit use case now requires Customer-Managed Key (BYOK) encryption to be enabled.
  • For the delegated_access use case, shared_access_key_enabled is now set to false.
  • Microsoft Defender for Storage (advanced_threat_protection) is now consistently enabled for use cases exposed to higher risks, such as delegated_access.

  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 containers, queues, and tables variables to create the desired resources within the Storage Account.

  For Example:

  • Before

    module "storage_account" {
      source  = "pagopa-dx/azure-storage-account/azurerm
      version = "~> 1.0"
      tier    = "l"
      # ...other variables...
    }

  • After

    module "storage_account" {
      source  = "pagopa-dx/azure-storage-account/azurerm
      version = "~> 2.0"
    
      use_case = "default"
    
      containers = [
        {
          name        = "container1"
          access_type = "private"
        },
        {
          name        = "container2"
          access_type = "private"
        }
      ]
    
      tables = [
        "table1",
        "table2"
      ]
    
      queues = [
        "queue1",
        "queue2"
      ]
    
      # ...other variables remain unchanged...
    }

  Note for already existing resources

  If containers, queues, or tables were previously created manually or through other means, use a moved file approach to map the existing resource addresses to the new module-managed addresses.

  1. Create a file named moved.tf in the same directory as your Terraform configuration.
  2. Add one moved block for each resource you want to reassign to the module. Inspect the terraform plan result carefully to see what Terraform intends to destroy/create.

  Example moved.tf block:

  moved {
    from = resource.azure_storage_container.old_container
    to   = module.storage_account.azure_storage_container.this[N]
  }

  Add one moved block per existing container/queue/table. Make sure the from address matches the existing resource address in your current configuration/state, and use the correct index N in the to address based on the order of the containers, queues, and tables lists you pass to the module so that internal indexes line up correctly.

[email protected]

Patch Changes

• 707b5cf: Add dns_forwarder outputs

[email protected]

Patch Changes

• 707b5cf: Add dns_forwarder outputs

[email protected]

Patch Changes

• 11ef401: Include oidc_provider_arn variable in examples and documentation

[email protected]

Patch Changes

• 707b5cf: First release

@pagopa/[email protected]

Minor Changes

• 051f215: Add Drift Detection workflow in the monorepo template

  Convert the existing workflow to accept parameters, so it is possible to generate jobs based on the selected environments.

• f638ad6: Install @devcontainers/cli as a project devDependency and use it to configure the DevContainers.

  With DevContainers, you can easily set up a consistent development environment across different machines. This is particularly useful for onboarding new team members, as they can quickly get started without worrying about local setup issues.

Patch Changes

• 155cb81: Add changeset configuration

• 7171d9d: Now, when turbo runs the typecheck task, it checks if it needs to build a package first.

  This is necessary when there is a workspace that depends on another workspace that needs to be built (e.g. a package with source code in src that needs to be compiled to dist).

• 155cb81: Integrate README with instruction to use changeset

• 38396b0: When scaffolding a new monorepo, the generator creates a README file as well

• fa4e825: Remove plop from peerDependencies block

  plop is not required to use @pagopa/monorepo-generator as a library, so it should not be listed in peerDependencies.

• 7171d9d: Instruct the scaffolder to install turbo