Skip to content
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

Support IP Range Reservation for Global Address. #469

Merged

Conversation

chrisst
Copy link
Contributor

@chrisst chrisst commented Sep 18, 2018


[all]

[terraform]

Supporting IP range reservation for global address

[puppet]

[puppet-bigquery]

[puppet-compute]

[puppet-container]

[puppet-dns]

[puppet-logging]

[puppet-pubsub]

[puppet-resourcemanager]

[puppet-sql]

[puppet-storage]

[chef]

[chef-compute]

[chef-container]

[chef-dns]

[chef-logging]

[chef-spanner]

[chef-sql]

[chef-storage]

[ansible]

@modular-magician
Copy link
Collaborator

I am a robot that works on MagicModules PRs!

I built this PR into one or more PRs on other repositories, and when those are closed, this PR will also be merged and closed.
depends: hashicorp/terraform-provider-google#2087


* VPC_PEERING - for peer networks

For regional internal addresses, it can be
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is the GlobalAddress resource, I don't think this value is worth documenting.

Since then it seems like there's only one value this field could take, I'm curious if it's something that we should actually give users the option to set. I assume there's a difference between setting it to VPC_PEERING and just not setting it at all?

products/compute/terraform.yaml Show resolved Hide resolved
- :VPC_PEERING
- :GCE_ENDPOINT
min_version: beta
- !ruby/object:Api::Type::String
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should be a resourceref, and then you won't need the diffsuppress in terraform.yaml since it'll happen automatically

@chrisst chrisst force-pushed the ip-range-reservation branch from 98e777b to 89aa567 Compare September 20, 2018 23:32
@chrisst chrisst force-pushed the ip-range-reservation branch from 89aa567 to 99f4a03 Compare September 20, 2018 23:33
@modular-magician
Copy link
Collaborator

I am (still) a robot that works on MagicModules PRs!

I just wanted to let you know that your changes (as of commit 0c97dc0) have been included in your existing downstream PRs.

@modular-magician
Copy link
Collaborator

I am (still) a robot that works on MagicModules PRs!

I just wanted to let you know that your changes (as of commit f985cec) have been included in your existing downstream PRs.

@modular-magician
Copy link
Collaborator

I am (still) a robot that works on MagicModules PRs!

I just wanted to let you know that your changes (as of commit e2c7b45) have been included in your existing downstream PRs.

Tracked submodules are build/puppet/_bundle build/puppet/auth build/puppet/bigquery build/puppet/compute build/puppet/sql build/puppet/storage build/puppet/spanner build/puppet/container build/puppet/dns build/puppet/pubsub build/puppet/resourcemanager build/chef/_bundle build/chef/auth build/chef/compute build/chef/sql build/chef/storage build/chef/spanner build/chef/container build/chef/dns build/chef/iam build/terraform build/ansible.
@modular-magician modular-magician merged commit 278dffb into GoogleCloudPlatform:master Sep 21, 2018
@chrisst chrisst deleted the ip-range-reservation branch September 21, 2018 16:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants