Open nupurg-ibm opened 8 months ago
Thanks, we are aware of the issue and already working on this fix
Just to validate I commented:
# output "vpc_resource_list" {
# description = "List of VPC with VSI and Cluster deployed on the VPC."
# value = [
# for vpc in module.vpc :
# {
# id = vpc.vpc_data.id
# name = vpc.vpc_data.name
# resource_group_id = vpc.vpc_data.resource_group
# region = var.region
# clusters = flatten([for cluster in ibm_container_vpc_cluster.cluster :
# cluster.id if cluster.vpc_id == vpc.vpc_data.id
# ])
# vsi = distinct(flatten([
# [
# for group in keys(local.vsi_map) :
# [
# for deployment in module.vsi[group].list :
# module.vsi[group].ids if vpc.vpc_data.id == deployment.vpc_id
# ]
# ]
# ]))
# }
# ]
# }
Now deployment happened but the existing_vpc_id which I passed with vpcs is not considered and it created new vpc and considered that one only for othe resources creation.
Thanks, Any timeline when we are planning to integrate existing vpc and existing subnet with landing-zone root module as discussed?
@nupurg-ibm The feature to add "existing_vpc_id" parameter to landing_zone inputs has not been released yet, and is still in development. We will need a new release of landing_zone for this feature.
I understand @toddgiguere . Do we have any tentative timeline when we are planning to release new version of landing_zone with this feature?
Do not have timeline yet, but I'm getting closer. When I have something working on my fork I could use some extra testing? I'll let you know.
Did terraform init which downloaded the landing-zone code
Then locally updated landing-zone-vpc module version to 7.13.1
Now tried adding existing_vpc_id under vpcs map of landing-zone module like below:
This gave error: