hashicorp / terraform-provider-azure-classic

Terraform Azure Classic (Service Management) provider
https://www.terraform.io/docs/providers/azure/
Mozilla Public License 2.0
2 stars 11 forks source link

Azure - possible to add Virtual Network Gateway resource #13

Closed hashibot closed 7 years ago

hashibot commented 7 years ago

This issue was originally opened by @davehodgson as hashicorp/terraform#4116. It was migrated here as part of the provider split. The original body of the issue is below.


Hi,

As part of putting together an Azure infrastructure I've noticed that while Virtual Network, Subnets and Security Groups exists, that a Virtual Network Gateway isn't possible, this is needed if you want to set up a Point-to-Site VPN, I can create it on the GUI after or via powershell/REST but it would be handy if I could do it via Terraform.

If it gets implemented then the ability to also upload a cert and download the configuration files that the GUI allows would be very handy.

A REST version of it is visible here: https://msdn.microsoft.com/en-us/library/azure/jj154119.aspx

I posted this on google groups originally: https://groups.google.com/forum/#!topic/terraform-tool/deNB8BWpRZ0

Cheers Dave

hashibot commented 7 years ago

This comment was originally opened by @davehodgson as https://github.com/hashicorp/terraform/issues/4116#issuecomment-162051563. It was migrated here as part of the provider split. The original comment is below.


FYI - until this resource is added, the suggestion on https://github.com/hashicorp/terraform/issues/4141 @jen20 works well.

I expanded it a little to suite my needs - I put the null_resource into a separate file so I can essentially remove the file and run apply (destroys it) and put it back and re-run apply (re-creates it) to re-run the script. I will also in time add a second file which calls a powershell script to destroy the network gateway.

resource "azure_virtual_network" "mynetwork" { // arguments }

resource "null_resource" "makevpngateway" { provisioner "local-exec" { command = "run provisioning script here" } depends_on = ["azure_virtual_network.mynetwork"] }

Cheers Dave

hashibot commented 7 years ago

This comment was originally opened by @tasquith as https://github.com/hashicorp/terraform/issues/4116#issuecomment-232345127. It was migrated here as part of the provider split. The original comment is below.


+1

hashibot commented 7 years ago

This comment was originally opened by @aleksandrov as https://github.com/hashicorp/terraform/issues/4116#issuecomment-263248968. It was migrated here as part of the provider split. The original comment is below.


+1

hashibot commented 7 years ago

This comment was originally opened by @wwwlicious as https://github.com/hashicorp/terraform/issues/4116#issuecomment-265115096. It was migrated here as part of the provider split. The original comment is below.


+1

hashibot commented 7 years ago

This comment was originally opened by @eerms as https://github.com/hashicorp/terraform/issues/4116#issuecomment-265142126. It was migrated here as part of the provider split. The original comment is below.


+1

hashibot commented 7 years ago

This comment was originally opened by @gloverc as https://github.com/hashicorp/terraform/issues/4116#issuecomment-300261996. It was migrated here as part of the provider split. The original comment is below.


+1

ghost commented 7 years ago

+1

ThinkBriK commented 7 years ago

+1

ghost commented 7 years ago

Hi,

I managed to add virtual gateway by running ARM template with Terraform template deployment https://www.terraform.io/docs/providers/azurerm/r/template_deployment.html

Issues is that resources is not destroyed with Terraform destroy, however, eventual if resource group is killed, it will also be killed.

Quite static, not sure how to push external variables to ARM template, there might be a way to do this.

Thanks

goblin23 commented 7 years ago

+1

apparentlymart commented 7 years ago

Hi all,

This azure provider is no longer developed and is preserved only for compatibility for existing configurations using it. All new development is happening in the azurerm provider, which uses the newer Azure Resource Manager API.

The "AzureRM" provider has support for a number of different network resources, and so may already have a resource to cover the use-case described here. If not, please feel free to open an issue in the azurerm provider repository, which is where all ongoing provider development is taking place.