feat: harden gcp-with-psc-exfiltration-protection module and example

[micheledaddetta-databricks]

Summary

Closes #165

Hardens the existing gcp-with-psc-exfiltration-protection module and example to align with repo conventions:

• Add validation blocks for databricks_account_id (UUID), google_region (PSC-supported regions enum), prefix (naming pattern), hive_metastore_ip (IPv4), and all CIDR variables
• Fix psc_subnet_cidr description (was incorrectly "CIDR for Spoke VPC")
• Expand module outputs from 2 to 10: VPC IDs, subnet IDs, network ID, and PSC endpoint IPs
• Add required_version >= 1.9.0 to both module and example
• Remove provider version pins (these are templates, not production modules)
• Organize variables with section comments
• Add .claude/ and CLAUDE.md to .gitignore

Test plan

• terraform fmt -check -recursive passes on changed files
• terraform validate passes on the module (requires provider init)
• Verify validation blocks reject invalid inputs (bad UUID, unsupported region, invalid CIDR)
• Verify new outputs are accessible from the example via module.gcp_with_data_exfiltration_protection.*

[Copilot]

Pull request overview

Hardens the existing gcp-with-psc-exfiltration-protection Terraform module and its example by adding input validations, expanding outputs, and aligning version/provider constraints and ignore rules with the repository’s template conventions.

Changes:

• Added variable validation for account ID, region, naming prefix, hive metastore IP, and CIDR inputs (module + example).
• Expanded module outputs to expose key network identifiers and PSC endpoint IPs.
• Standardized Terraform required_version and removed provider version pins; updated .gitignore to exclude Claude tooling files.

Reviewed changes

Copilot reviewed 5 out of 6 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
modules/gcp-with-psc-exfiltration-protection/variables.tf	Adds variable organization + validation blocks for core inputs.
modules/gcp-with-psc-exfiltration-protection/terraform.tf	Sets required_version >= 1.9.0 and keeps providers unpinned.
modules/gcp-with-psc-exfiltration-protection/outputs.tf	Adds outputs for VPC/subnet/network IDs and PSC endpoint IPs.
examples/gcp-with-psc-exfiltration-protection/variables.tf	Mirrors module validations and reorganizes variable sections.
examples/gcp-with-psc-exfiltration-protection/terraform.tf	Sets required_version >= 1.9.0 and removes provider version pins.
.gitignore	Ignores .claude/ and CLAUDE.md.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[alexott]

• [P1] Restore provider constraints in the example. The PR removes the databricks and google version constraints from examples/gcp-with-psc-exfiltration-protection/terraform.tf, and this repo does not commit Terraform lock files. On a fresh init of this branch Terraform selected databricks 1.117.0 and google 7.35.0 instead of the previously documented/tested databricks >=1.81.1 and google 6.17.0. That makes the example drift to whatever the registry latest is and can break users without any repo change. Please keep explicit constraints in the root example, or otherwise add an intentional lock/compatibility story.

• [P2] Regenerate the terraform-docs README blocks for the changed module and example. The PR adds required_version >= 1.9.0, changes input descriptions, and adds several module outputs, but modules/gcp-with-psc-exfiltration-protection/README.md still says No requirements and only lists workspace_id/workspace_url outputs. examples/gcp-with-psc-exfiltration-protection/README.md also still documents the removed provider requirements and old input descriptions. Running terraform-docs markdown table on both directories produces updates, so the generated docs are currently stale.

[micheledaddetta-databricks]

Hello @alexott , changes implemented as required. Let me know if additional changes are required.