Warn about specifying ip_version and ip_address together #616
Conversation
If you try and specify them together you will get this error: google_compute_global_forwarding_rule.your-rule: Error creating Global Forwarding Rule: googleapi: Error 400: Invalid value for field 'resource.ipVersion': 'IPV4'. Both IP Version and IP Address cannot be specified., invalid
|
I can't see any docs for it either, but I got an error when I tried to add $ tfapply
google_compute_global_forwarding_rule.new-ipv4: Creating...
ip_address: "" => "<snip>"
ip_protocol: "" => "<computed>"
ip_version: "" => "IPV4"
label_fingerprint: "" => "<computed>"
name: "" => "new-forwarding-rule"
port_range: "" => "80"
self_link: "" => "<computed>"
target: "" => "https://www.googleapis.com/compute/v1/projects/<snip>/global/targetHttpProxies/<snip>"
Error applying plan:
1 error(s) occurred:
* google_compute_global_forwarding_rule.new-ipv4: 1 error(s) occurred:
* google_compute_global_forwarding_rule.new-ipv4: Error creating Global Forwarding Rule: googleapi: Error 400: Invalid value for field 'resource.ipVersion': 'IPV4'. Both IP Version and IP Address cannot be specified., invalid
Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure. |
|
How very bizarre. Let me try a few different types of forwarding rules out (I know there are a few configurations supported that have different requirements) and make sure it's not valid for any of them, then we can go ahead and merge it. In lieu of documentation anywhere else, though, I just want to be sure that this actually holds in all cases. |
|
My assumption was that |
|
I agree with your assumption @danielcompton and like the clarification in the docs. |
…-google * 'master' of https://github.com/olvesh/terraform-provider-google: (24 commits) Cleanup after v1.14.0 release v1.14.0 Update CHANGELOG.md Add new google_compute_regions (hashicorp#1603) Update CHANGELOG.md Fix forwarding rule data source test (hashicorp#1606) Update CHANGELOG.md Fix redis authorized network and tests. The Redis API currently only accepts partial links. The tests weren't failing because they weren't actually using the network (oops). There were a few other test issues that I fixed while I was there. Fixes hashicorp#1571. (hashicorp#1599) update auth docs (hashicorp#1587) Fix network_tier tests. Add documentation for network tier (hashicorp#1593) Warn about ip_version with ip_address in global forwarding rule (hashicorp#616) Update CHANGELOG.md add support for network tiers (hashicorp#1530) Update CHANGELOG.md Allow using in repo configuration for cloudbuild trigger (hashicorp#1557) Update CHANGELOG.md add update support for redis (hashicorp#1590) Update CHANGELOG.md Added GCP Netblock Data Source (hashicorp#1416) (hashicorp#1580) ...
…icorp#616) If you try and specify them together you will get this error: google_compute_global_forwarding_rule.your-rule: Error creating Global Forwarding Rule: googleapi: Error 400: Invalid value for field 'resource.ipVersion': 'IPV4'. Both IP Version and IP Address cannot be specified., invalid
|
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 👉 hashibot-feedback@hashicorp.com. Thanks! |
ghost
locked and limited conversation to collaborators
No description provided.