-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable Deployment or Dependency on a VNet in a Separate Resource Group #64
Conversation
@genevieve who would be the right people to talk to about getting this merged? |
@jseely I believe @nmahoney-pivotal @Polar-Beard have the power 🙌 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @jseely. We've got a couple questions for you :)
@jseely We are going to revert this merge. |
@jseely Please make another PR when ready. This one is stuck in a merged state. |
ok will do, sorry for the delay in getting a fix |
This reverts commit e136140.
This enables networking resources to be deployed into a separate resource group. Ideally this will end up being networking resources pre-configured in an RG, provisioned by the IT department, with read only access for the Service Principal being used to deploy PAS/PKS/Control Plane.
Network Resources can optionally be deployed into a separate RG by:
pcf_vnet_rg
, in tfvars, to the name of the RG where the network resources are to be deployedThe VNet here can optionally be pre-existing by:
create_vnet = false
in tfvarspcf_vnet = "<name_of_existing_vnet>"
in tfvarsFeatures: