Skip to content

Conversation

@jhanavi
Copy link
Contributor

@jhanavi jhanavi commented Dec 3, 2025

No description provided.

@jhanavi jhanavi requested review from a team and imrannayer as code owners December 3, 2025 22:06
@jhanavi jhanavi changed the title Generate output type in metadata for network chore: Generate output type in metadata for network Dec 3, 2025
bgp_always_compare_med: bool
bgp_best_path_selection_mode: string
bgp_inter_region_cost: string
delete_default_routes_on_create: bool
Copy link

@Ayushi001 Ayushi001 Dec 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could u confirm where the fields and types of network output are checked from? from /outputs.tf
output "network" {
value = module.vpc
description = "The created network"
}

and module.vpc point to
modules/vpc/outputs.tf:

output "network" {
value = google_compute_network.network
description = "The VPC resource being created"
}

and some fields here are not present in resource "google_compute_network" "network" { ...} at modules/vpc/main.tf like gateway_ipv4

are these fields of network output type verified from terraform apply results of this module?

description: The IPs and CIDRs of the subnets being created
type:
- tuple
- []

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why are empty values in type added for some output types like subnets, subnets_flow_logs etc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants