Add Terraform backend when creating repository resources

[kin0992]

This pull request introduces enhancements to the monorepo generator, specifically improving the Terraform infrastructure setup by dynamically configuring the backend state based on the selected cloud provider (CSP). It adds new prompt variables for both AWS and Azure backends, updates documentation, and implements the backend configuration in the generated Terraform files.

Closes CES-1278

[changeset-bot]

🦋 Changeset detected

Latest commit: a9e6fdb

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@pagopa/monorepo-generator	Patch
@pagopa/dx-cli	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[codecov-commenter]

Codecov Report

❌ Patch coverage is 0% with 47 lines in your changes missing coverage. Please review.
✅ Project coverage is 45.56%. Comparing base (8abeb56) to head (ae47d0b).
⚠️ Report is 68 commits behind head on main.

Files with missing lines	Patch %	Lines
packages/monorepo-generator/src/index.ts	0.00%	47 Missing ⚠️

❌ Your project status has failed because the head coverage (45.56%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #911       +/-   ##
===========================================
- Coverage   67.85%   45.56%   -22.30%     
===========================================
  Files          31       39        +8     
  Lines         840     1543      +703     
  Branches      146      184       +38     
===========================================
+ Hits          570      703      +133     
- Misses        258      826      +568     
- Partials       12       14        +2     

Files with missing lines	Coverage Δ
packages/monorepo-generator/src/index.ts	0.45% <0.00%> (ø)

... and 6 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull Request Overview

This pull request adds support for conditional Terraform backend configuration to the monorepo generator, allowing users to automatically configure state storage based on their selected cloud provider (AWS or Azure). It introduces user prompts for backend-specific details and dynamically injects the appropriate backend configuration into generated Terraform files.

• Adds new Handlebars template partials for AWS and Azure backend state configuration
• Extends user prompts to collect cloud provider-specific backend configuration details
• Implements dynamic partial loading logic to select the correct backend template based on user input

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
packages/monorepo-generator/templates/monorepo/infra/repository/providers.tf.hbs	Replaces TODO comment with dynamic backend state partial inclusion
packages/monorepo-generator/templates/monorepo/infra/azure/partials/backend-state.tf.hbs	New Azure backend configuration template with azurerm backend
packages/monorepo-generator/templates/monorepo/infra/aws/partials/backend-state.tf.hbs	New AWS backend configuration template with S3 backend
packages/monorepo-generator/src/index.ts	Adds new prompts, backend partial selection logic, and updates action dependencies
packages/monorepo-generator/README.md	Documents new template variables and updates formatting
.changeset/swift-beers-deny.md	Changeset documentation for the feature addition

[lucacavallaro]

thought: in my opinion this question should not be asked, we have to decide a region for our consumers.

[Krusty93]

It's difficult to put a default for region while keeping the tool agnostic from PagoPA habits.
Perhaps we could develop a CLI plugin for each business project we support to provide the right values to the user?
We already have a solution like this and it is actually implemented in part via a Terraform module, but the CLI scenario could expand it

[gunzip]

what about having all defaults in some config.yaml ?

[Krusty93]

How are they fetched?

[lucacavallaro]

question: can't this be pre-filled following a convention?

[kin0992]

something like ${prefix}-${envShort}-${locationShort}-terraform-rg-01?