Public IP support for existing vnet deployment #42
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While using this driver I ran into the scenario that I would like to provision my VM using Kitchen in an existing VNET on Azure. However the VM in the VNET is accessible from my local network because there is no gateway in between. There for I would like the possibility to expose a public IP when the VNET is specified.
Implementation details
public_ip
azurerm.rb
file