Create a virtual_network_gateway with azurerm #17
Labels
Comments
|
@dominik-lekse Thank you for working on this. My team needs these resources. |
apparentlymart
pushed a commit
that referenced
this issue
Jul 22, 2017
* initial commit - 101-vm-from-user-image * changed branch name * not deploying - storage problems * provisions vm but image not properly prepared * storage not correct * provisions properly * changed main.tf to azuredeploy.tf * added tfvars and info for README * tfvars ignored and corrected file ext * added CI config; added sane defaults for variables; updated deployment script, added mac specific deployment for local testing * deploy.sh to be executable * executable deploy files * added CI files; changed vars * prep for PR * removal of old folder * prep for PR * wrong args for travis * more PR prep * updated README * commented out variables in terraform.tfvars * Topic 101 vm from user image (#2) * initial commit - 101-vm-from-user-image * added tfvars and info for README * added CI config; added sane defaults for variables; updated deployment script, added mac specific deployment for local testing * prep for PR * added new template * oops, left off master * prep for PR * correct repository for destination * renamed scripts to be more intuitive; added check for docker * merge vm simple; vm from image * initial commit * deploys locally * updated deploy * consolidated deploy and after_deploy into a single script; simplified ci process; added os_profile_linux_config * added terraform show * changed to allow http & https (like ARM tmplt) * changed host_name & host_name variable desc * added az cli check * on this branch, only build test_dir; master will aggregate all the examples * merge master * added new constructs/naming for deploy scripts, etc. * suppress az login output * suppress az login output * forgot about line breaks * breaking build as an example * fixing broken build example * work in progress * merge of CI config * fixed grammar in readme * prep for PR * deploys locally * deploys locally * small README change * took out armviz button and minor README changes * changed host_name * fixed merge conflicts * changed host_name variable * updating Hashicorp's changes to merged simple linux branch * updating files to merge w/master and prep for Hashicorp pr * Revert "updating files to merge w/master and prep for Hashicorp pr" This reverts commit b850cd5d2a858eff073fc5a1097a6813d0f8b362. * Revert "updating Hashicorp's changes to merged simple linux branch" This reverts commit dbaf8d14a9cdfcef0281919671357f6171ebd4e6. * added provider to main.tf * took out armviz button; resolved conflicts in .travis.yml * removing vm from user image example from this branch * removed old branch * azure-2-vms-loadbalancer-lbrules (#13) * initial commit * need to change lb_rule & nic * deploys locally * updated README * updated travis and deploy scripts for Hari's repo * renamed deploy script * clean up * prep for PR * updated readme * fixing conflict in .travis.yml * add CI build tag * azure-traffic-manager-vm (#17) adding example of azure traffic manager * prepped for Hashicorp PR * merging with hashicorp master
apparentlymart
pushed a commit
that referenced
this issue
Jul 22, 2017
…ion (#14341) * initial commit - 101-vm-from-user-image * changed branch name * not deploying - storage problems * provisions vm but image not properly prepared * storage not correct * provisions properly * changed main.tf to azuredeploy.tf * added tfvars and info for README * tfvars ignored and corrected file ext * added CI config; added sane defaults for variables; updated deployment script, added mac specific deployment for local testing * deploy.sh to be executable * executable deploy files * added CI files; changed vars * prep for PR * removal of old folder * prep for PR * wrong args for travis * more PR prep * updated README * commented out variables in terraform.tfvars * Topic 101 vm from user image (#2) * initial commit - 101-vm-from-user-image * added tfvars and info for README * added CI config; added sane defaults for variables; updated deployment script, added mac specific deployment for local testing * prep for PR * added new template * oops, left off master * prep for PR * correct repository for destination * renamed scripts to be more intuitive; added check for docker * merge vm simple; vm from image * initial commit * deploys locally * updated deploy * consolidated deploy and after_deploy into a single script; simplified ci process; added os_profile_linux_config * added terraform show * initial commit * changed to allow http & https (like ARM tmplt) * changed host_name & host_name variable desc * added az cli check * on this branch, only build test_dir; master will aggregate all the examples * deploys locally; need to fix deploy scripts * chmod for deploy.ci.sh * corrected deploy.ci.sh * added resource group var to travis.yml * merge master * edited travis.yml * fixed error on travis.yml * added new constructs/naming for deploy scripts, etc. * took rg variable out; added destroy resources to travis.yml * cleaned up commented out lines in deploy.ci.sh * suppress az login output * suppress az login output * forgot about line breaks * breaking build as an example * fixing broken build example * merge of CI config * prep for PR * cleanup for PR * fixed grammar in readme * prep for PR * took out armviz button and minor README changes * changed host_name * fixed merge conflicts * changed host_name variable * updating Hashicorp's changes to merged simple linux branch * updating files to merge w/master and prep for Hashicorp pr * Revert "updating files to merge w/master and prep for Hashicorp pr" This reverts commit b850cd5d2a858eff073fc5a1097a6813d0f8b362. * Revert "updating Hashicorp's changes to merged simple linux branch" This reverts commit dbaf8d14a9cdfcef0281919671357f6171ebd4e6. * removing vm from user image example from this branch * removed old branch * added depends_on resource group for workaround to bug * resolving conflicts * restoring previous examples/resolving merge conflict * resolving conflict * updated .travis.yml * azure-2-vms-loadbalancer-lbrules (#13) * initial commit * need to change lb_rule & nic * deploys locally * updated README * updated travis and deploy scripts for Hari's repo * renamed deploy script * clean up * prep for PR * updated readme * fixing conflict in .travis.yml * add CI build tag * updated descriptions * azure-traffic-manager-vm (#17) adding example of azure traffic manager * azure-vnet-to-vnet-peering (#20) adding vnet-to-vnet-peering example * returning .travis.yml to correct state * azure-search-create (#21) adding azure-search-create example * merging Hashicorp master into this branch * added graph to README * removing unmerged examples
apparentlymart
pushed a commit
that referenced
this issue
Jul 22, 2017
* initial commit - 101-vm-from-user-image * changed branch name * not deploying - storage problems * provisions vm but image not properly prepared * storage not correct * provisions properly * changed main.tf to azuredeploy.tf * added tfvars and info for README * tfvars ignored and corrected file ext * added CI config; added sane defaults for variables; updated deployment script, added mac specific deployment for local testing * deploy.sh to be executable * executable deploy files * added CI files; changed vars * prep for PR * removal of old folder * prep for PR * wrong args for travis * more PR prep * updated README * commented out variables in terraform.tfvars * Topic 101 vm from user image (#2) * initial commit - 101-vm-from-user-image * added tfvars and info for README * added CI config; added sane defaults for variables; updated deployment script, added mac specific deployment for local testing * prep for PR * added new template * oops, left off master * prep for PR * correct repository for destination * renamed scripts to be more intuitive; added check for docker * merge vm simple; vm from image * initial commit * deploys locally * updated deploy * consolidated deploy and after_deploy into a single script; simplified ci process; added os_profile_linux_config * added terraform show * changed to allow http & https (like ARM tmplt) * changed host_name & host_name variable desc * added az cli check * on this branch, only build test_dir; master will aggregate all the examples * merge master * added new constructs/naming for deploy scripts, etc. * suppress az login output * suppress az login output * forgot about line breaks * breaking build as an example * fixing broken build example * merge of CI config * fixed grammar in readme * prep for PR * took out armviz button and minor README changes * changed host_name * fixed merge conflicts * changed host_name variable * updating Hashicorp's changes to merged simple linux branch * updating files to merge w/master and prep for Hashicorp pr * Revert "updating files to merge w/master and prep for Hashicorp pr" This reverts commit b850cd5d2a858eff073fc5a1097a6813d0f8b362. * Revert "updating Hashicorp's changes to merged simple linux branch" This reverts commit dbaf8d14a9cdfcef0281919671357f6171ebd4e6. * removing vm from user image example from this branch * removed old branch * initial commit - azure search create * removing graph from README * azure-2-vms-loadbalancer-lbrules (#13) * initial commit * need to change lb_rule & nic * deploys locally * updated README * updated travis and deploy scripts for Hari's repo * renamed deploy script * clean up * prep for PR * updated readme * fixing conflict in .travis.yml * add CI build tag * updated .travis.yml to have the correct branch; validated resource with azure cli * deleted commented out item in deploy script * azure-traffic-manager-vm (#17) adding example of azure traffic manager * azure-vnet-to-vnet-peering (#20) adding vnet-to-vnet-peering example * returning .travis.yml to correct state * correcting .travis.yml * merging with master * merging Hashicorp master into this branch * removing unmerged example * changed README
|
Also just ran into this missing capability in TF. What makes it unfortunate apparently VnetGW are required to exist in the same resource group as the VNet they're connected to... 🙁 So managing vnets/subnets with TF is a forced config drift situation... (Wishing I knew go and could contrib right about now...) |
|
Hey @samirageb
This has been implemented by @dominik-lekse in PR #133 - we're just waiting on Microsoft to fix an API before we can proceed (which is scheduled for mid-month)
That's good to know - do we add something to that effect in the documentation @dominik-lekse?
That shouldn't be an issue - would it be possible to open a separate issue to discuss that? Thanks! |
|
@tombuildsstuff Thanks for the updates. Re: config drift, I was simply referring to the fact that VNETs/Subnets can be controlled via TF, but VNetGW's can't, so I have RG's that are partially managed by TF. (No new issue req'd) |
|
@samirageb I would also really like this to be finished and merged however there is the work-around of using the arm template resource to create the virtual network gateway and connection resources. I'm in the process of getting this working myself. If it would be helpful I could post a gist of an example configuration. |
|
I suggest closing this issue. Duplicate and it has now been addressed as of release v1.1.0 @tombuildsstuff just because I know you have privs to close :) |
|
Thanks for the ping @kmcquade :) |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
ghost
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue was originally opened by @dpnl87 as hashicorp/terraform#8372. It was migrated here as part of the provider split. The original body of the issue is below.
I would like to have to possibility to create virtual network gateways with Terraform and the Azurerm provider. Currently there is no support for it so we still need to do manual actions on Azure.
Its used to link a network interface to a ExpressRoute.
If you need any additional information or require testing assistance I'm more then happy to help out.
The text was updated successfully, but these errors were encountered: