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

feat!: update TPG version constraints to 4.0 #1129

Merged
merged 35 commits into from
Jan 22, 2022

Conversation

bharathkkb
Copy link
Member

based off of #1071 since I didnt have permission to push to the fork branch

@bharathkkb bharathkkb requested review from Jberlinsky and a team as code owners January 19, 2022 22:47
@bharathkkb bharathkkb marked this pull request as draft January 19, 2022 22:48
@comment-bot-dev
Copy link

comment-bot-dev commented Jan 19, 2022

Thanks for the PR! 🚀
✅ Lint checks have passed.

@bharathkkb bharathkkb force-pushed the 1071-branch-provider-update branch 2 times, most recently from 596bcbb to 0dccbb7 Compare January 21, 2022 02:02
* addresses warning about multiple provider blocks
* temporary change until new version is released
* temporary change until new version of that dependency is released
@bharathkkb bharathkkb marked this pull request as ready for review January 21, 2022 15:18
@bharathkkb bharathkkb changed the title [WIP]: feat: update TPG version constraints to allow 4.0 feat!: update TPG version constraints to allow 4.0 Jan 21, 2022
@@ -112,6 +112,7 @@ resource "google_compute_firewall" "master_webhooks" {
direction = "INGRESS"

source_ranges = [local.cluster_endpoint_for_nodes]
source_tags = []
Copy link
Member Author

Choose a reason for hiding this comment

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

Workaround for hashicorp/terraform-provider-google#10494. Long term fix maybe GoogleCloudPlatform/magic-modules#5526 but will need to validate.

@bharathkkb bharathkkb changed the title feat!: update TPG version constraints to allow 4.0 feat!: update TPG version constraints to 4.0 Jan 21, 2022
@bharathkkb
Copy link
Member Author

@morgante PTAL since I rebased this and added a few commits

}
```

### Acceptable values for node_metadata modified
Copy link
Contributor

Choose a reason for hiding this comment

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

Instead of requiring users to change this, I think we can provide a mapping at very low effort to ourselves. Could you add that?

Copy link
Member Author

Choose a reason for hiding this comment

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

I updated the doc in e83bfc3 to make this a recommendation instead, encouraging users to switch to values that are supported by the provider.

docs/upgrading_to_v8.0.md Outdated Show resolved Hide resolved
Copy link
Contributor

@morgante morgante left a comment

Choose a reason for hiding this comment

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

Just some nits - go ahead and merge once resolved.

autogen/main/main.tf.tmpl Outdated Show resolved Hide resolved
autogen/main/variables.tf.tmpl Outdated Show resolved Hide resolved
bharathkkb and others added 2 commits January 21, 2022 15:00
Co-authored-by: Morgante Pell <morgantep@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants