Terraform retrieve CIDR/Prefix from existing VNETs/subnets





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















In Terraform, I want to create a route table for an existing subnet. To achieve the desired end result, I need to pull the CIDR/Prefix for the VNET. The VNET CIDR value is not known beforehand, the only values I know before launch is the VNET's name and Resource Group.



I would like to take the VNET CIDR/Prefix and insert it as a destination in the route table.



data "azurerm_virtual_network" "vnet" {
name = "${var.vnet_name}"
resource_group_name = "${var.vnet_rg}"
}

module "routetable" {
source = "modules/routetable"
route_table_name = "${var.route_table_name}"
resource_group_name =
"${data.azurerm_resource_group.vnet.name}"
location = "eastus"
route_prefixes = ["0.0.0.0/0", "${EXISTING_VNET_CIDR_HERE}"]


route_nexthop_types = ["VirtualAppliance", "VirtualAppliance"]
route_names = ["route1", "route2"]
}









share|improve this question





























    0















    In Terraform, I want to create a route table for an existing subnet. To achieve the desired end result, I need to pull the CIDR/Prefix for the VNET. The VNET CIDR value is not known beforehand, the only values I know before launch is the VNET's name and Resource Group.



    I would like to take the VNET CIDR/Prefix and insert it as a destination in the route table.



    data "azurerm_virtual_network" "vnet" {
    name = "${var.vnet_name}"
    resource_group_name = "${var.vnet_rg}"
    }

    module "routetable" {
    source = "modules/routetable"
    route_table_name = "${var.route_table_name}"
    resource_group_name =
    "${data.azurerm_resource_group.vnet.name}"
    location = "eastus"
    route_prefixes = ["0.0.0.0/0", "${EXISTING_VNET_CIDR_HERE}"]


    route_nexthop_types = ["VirtualAppliance", "VirtualAppliance"]
    route_names = ["route1", "route2"]
    }









    share|improve this question

























      0












      0








      0








      In Terraform, I want to create a route table for an existing subnet. To achieve the desired end result, I need to pull the CIDR/Prefix for the VNET. The VNET CIDR value is not known beforehand, the only values I know before launch is the VNET's name and Resource Group.



      I would like to take the VNET CIDR/Prefix and insert it as a destination in the route table.



      data "azurerm_virtual_network" "vnet" {
      name = "${var.vnet_name}"
      resource_group_name = "${var.vnet_rg}"
      }

      module "routetable" {
      source = "modules/routetable"
      route_table_name = "${var.route_table_name}"
      resource_group_name =
      "${data.azurerm_resource_group.vnet.name}"
      location = "eastus"
      route_prefixes = ["0.0.0.0/0", "${EXISTING_VNET_CIDR_HERE}"]


      route_nexthop_types = ["VirtualAppliance", "VirtualAppliance"]
      route_names = ["route1", "route2"]
      }









      share|improve this question














      In Terraform, I want to create a route table for an existing subnet. To achieve the desired end result, I need to pull the CIDR/Prefix for the VNET. The VNET CIDR value is not known beforehand, the only values I know before launch is the VNET's name and Resource Group.



      I would like to take the VNET CIDR/Prefix and insert it as a destination in the route table.



      data "azurerm_virtual_network" "vnet" {
      name = "${var.vnet_name}"
      resource_group_name = "${var.vnet_rg}"
      }

      module "routetable" {
      source = "modules/routetable"
      route_table_name = "${var.route_table_name}"
      resource_group_name =
      "${data.azurerm_resource_group.vnet.name}"
      location = "eastus"
      route_prefixes = ["0.0.0.0/0", "${EXISTING_VNET_CIDR_HERE}"]


      route_nexthop_types = ["VirtualAppliance", "VirtualAppliance"]
      route_names = ["route1", "route2"]
      }






      azure terraform






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 3 at 16:02









      chew224chew224

      658




      658
























          1 Answer
          1






          active

          oldest

          votes


















          2














          just use data you are getting from the vnet:



          ${data.azurerm_virtual_network.vnet.address_spaces}


          the only issue - assress_spaces is an array (i think its called list in terraforms terms).






          share|improve this answer



















          • 1





            Worked like a charm. I was using .vnet.address_space not .vnet.address_spaces. Terraform's documentation on attribute IDs uses address_space... interesting.

            – chew224
            Jan 3 at 18:04














          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54025840%2fterraform-retrieve-cidr-prefix-from-existing-vnets-subnets%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          just use data you are getting from the vnet:



          ${data.azurerm_virtual_network.vnet.address_spaces}


          the only issue - assress_spaces is an array (i think its called list in terraforms terms).






          share|improve this answer



















          • 1





            Worked like a charm. I was using .vnet.address_space not .vnet.address_spaces. Terraform's documentation on attribute IDs uses address_space... interesting.

            – chew224
            Jan 3 at 18:04


















          2














          just use data you are getting from the vnet:



          ${data.azurerm_virtual_network.vnet.address_spaces}


          the only issue - assress_spaces is an array (i think its called list in terraforms terms).






          share|improve this answer



















          • 1





            Worked like a charm. I was using .vnet.address_space not .vnet.address_spaces. Terraform's documentation on attribute IDs uses address_space... interesting.

            – chew224
            Jan 3 at 18:04
















          2












          2








          2







          just use data you are getting from the vnet:



          ${data.azurerm_virtual_network.vnet.address_spaces}


          the only issue - assress_spaces is an array (i think its called list in terraforms terms).






          share|improve this answer













          just use data you are getting from the vnet:



          ${data.azurerm_virtual_network.vnet.address_spaces}


          the only issue - assress_spaces is an array (i think its called list in terraforms terms).







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 3 at 17:49









          4c74356b414c74356b41

          33.3k42758




          33.3k42758








          • 1





            Worked like a charm. I was using .vnet.address_space not .vnet.address_spaces. Terraform's documentation on attribute IDs uses address_space... interesting.

            – chew224
            Jan 3 at 18:04
















          • 1





            Worked like a charm. I was using .vnet.address_space not .vnet.address_spaces. Terraform's documentation on attribute IDs uses address_space... interesting.

            – chew224
            Jan 3 at 18:04










          1




          1





          Worked like a charm. I was using .vnet.address_space not .vnet.address_spaces. Terraform's documentation on attribute IDs uses address_space... interesting.

          – chew224
          Jan 3 at 18:04







          Worked like a charm. I was using .vnet.address_space not .vnet.address_spaces. Terraform's documentation on attribute IDs uses address_space... interesting.

          – chew224
          Jan 3 at 18:04






















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54025840%2fterraform-retrieve-cidr-prefix-from-existing-vnets-subnets%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

          'app-layout' is not a known element: how to share Component with different Modules

          SQL update select statement