feat: updating secure blueprint to cloud run v2

[marcelorobj]

Description

This pull request updates the core blueprint/project to version 2 (v2). This update introduces the Cloud Run v2 API module as the core engine for deployments, bringing native support for advanced features like Direct VPC Egress, liveness/startup probes, and Gen2 execution environments to ensure our infrastructure aligns with the latest v2 specifications.

Specifically, the following changes were made:

• Updated Core Dependencies: The secure-cloud-run-core module's source has been bumped to its v2 equivalent (source = "../v2"), transitioning the underlying infrastructure to use Google Cloud Run v2 Terraform resources.
• Refactored Secure Cloud Run Core & Wrapper Modules: Restructured the modules to support a suite of new v2 features. New variables were introduced, including startup_probe, liveness_probe, execution_environment (defaults to Gen2), vpc_network_interface (for Direct VPC Egress), enable_prometheus_sidecar, iap_members, and cloud_run_deletion_protection.
• Refactored V2 Module & Domain Mapping: Integrated google_cloud_run_domain_mapping natively into the v2 module and core modules, adding corresponding variables (verified_domain_name, certificate_mode, force_override) and outputs (domain_map_id, domain_map_status, service_url).
• Refactored Serverless Network Module: Made the google_vpc_access_connector conditionally created (only created if connector_name is provided), allowing for deployments that strictly use Direct VPC Egress without requiring a Serverless VPC Access Connector.
• Removed/Updated Deprecated Variables: Removed the legacy requests variable from the core module. Updated vpc_egress_value defaults and allowed values to use uppercase enums (PRIVATE_RANGES_ONLY, ALL_TRAFFIC) to comply with v2 API standards. traffic_split was also updated to utilize optional attributes.

This change allows users to leverage the new v2 features while maintaining a secure and scalable environment.

Related Issues/PRs

• N/A

Type of Change

• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected) (Note: v2 updates are usually breaking changes due to variable structure shifts and underlying resource changes)
• Documentation update

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (README.md, metadata.yaml)
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

How Has This Been Tested?

This feature has been tested by deploying the updated v2 blueprint in a sandbox environment. Verification included:

• Confirming the successful deployment of Secure Cloud Run services using the new v2 module structure.
• Verifying that Serverless VPC Access Connectors, Direct VPC Egress configuration and Gen2 execution environments behave as expected.
• Verifying that the conditional creation of the VPC Access Connector works properly.

Important Notes

• Variable Formatting Changes: The vpc_egress_value now requires uppercase strings (e.g., PRIVATE_RANGES_ONLY instead of private-ranges-only).
• VPC Connectivity: Users can now choose between using a traditional Serverless VPC Access Connector (vpc_connector_id) or utilizing Direct VPC Egress by providing vpc_network_interface.

[apeabody]

/gcbrun

[github-actions]

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

[marcelorobj]

/gcbrun