Thread
#general
    i

    incalculable-garden-60162

    2 months ago
    Hi, I need help to resolve the following case i face now, Project -1 : First I create "VPC-A" with a Private Subnet without any specific routes. Project - 2: Secondly I create another VPC "VPC-B" with a Public Subnet and 2 Private Subnets. Along with this I establish Peering Connection between these two VPCs and once the peering connection is made, new route tables are created so that the Private Subnets of "VPC B" can "ingress" into Private Subnets of "VPC A". So far so good. Now, I need to add routes to the already existing route table of the Private Subnet of "VPC - A" to egress to Private Subnets of "VPC-B" via the "Peering gateway". Like this I may in future need to add more routes to an existing route table. Is this possible ? i am not trying to import already existing route table outside the pulumi stack. I tried different means and many times i got exception as "trying to create a new route table with an existing name, try give an unique name". Need a helping hand in this .
    e

    echoing-dinner-19531

    2 months ago
    Oh circular updates are hard! We had a blog post about this a while ago which discussed some hacks you can do now, and also some proposals for how we could support this properly (tracked at https://github.com/pulumi/pulumi/issues/3021). Might be one of the ideas from the blog posts would work for this, but also vote and comment on that issue so we can track use cases for this.
    b

    billowy-army-68599

    2 months ago
    @incalculable-garden-60162 what code do you currently have?
    i

    incalculable-garden-60162

    2 months ago
    Hi, I solved this issue using getRouteTable() . I created the Route table as a separate project. So if I need to add Routes in the future, I can just add route table configuration code and "pulumi up" this Route table code file and not touch the main program. I earlier worked in the AWS AppConfig service where we separate the configuration files from the main code and then deploy them separately. I used that logic here and it worked.