-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Cherry-picks to support 1.20.0 release. #2567
Conversation
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.
Just a couple of questions for things that jumped out at me that I couldn't find the rationale for. Sorry if the rationale is in the commits, I had a hard time trying to track them down.
My only real concern is that these changes are included as part of an entire commit that has been reviewed, and are included on purpose. Basically, that they're not mistakes with the cherrypicking.
@@ -12,22 +12,22 @@ import ( | |||
|
|||
var IamComputeSubnetworkSchema = map[string]*schema.Schema{ | |||
"subnetwork": { | |||
Deprecated: "This resource is in beta and will be removed from this provider. Use it in the the google-beta provider instead. See https://terraform.io/docs/providers/google/provider_versions.html for more details.", | |||
Deprecated: "This field is in beta and will be removed from this provider. Use it in the the google-beta provider instead. See https://terraform.io/docs/providers/google/provider_versions.html for more details.", |
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.
What's going on here?
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.
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.
I'm agreed on the resource text being preferred here, but don't know how possible that is.
We have got a couple of fun ones here.
|
a224551
to
62f53ea
Compare
<!-- This change is generated by MagicModules. --> /cc @rileykarson
<!-- This change is generated by MagicModules. --> /cc @danawillow
<!-- This change is generated by MagicModules. --> /cc @rileykarson
<!-- This change is generated by MagicModules. --> /cc @danawillow
<!-- This change is generated by MagicModules. --> /cc @danawillow
<!-- This change is generated by MagicModules. --> /cc @danawillow
blocking GoogleCloudPlatform/magic-modules#630 This resource won't be tested between this merging and the MM pr merging
<!-- This change is generated by MagicModules. --> /cc @rileykarson
<!-- This change is generated by MagicModules. --> /cc @danawillow Fixes #2286
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.
I don't see anything egregiously wrong running through at a high level, and every code change I looked at in depth was correct.
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.
Skimmed through, looks reasonable
Co-Authored-By: ndmckinley <[email protected]>
2a96eab
What! I accepted Riley's suggestion and now it told me I've dismissed your stale approvals! Man, I'm never clicking that button again. |
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.
oh that's so sad
All right that's not good. We're gonna fix that. |
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 👉 [email protected]. Thanks! |
This is a branch made up of every cherrypick I could easily include in this release (and some that weren't super easy... but it all compiles now and I'll be running CI tests ASAP).
Here's what we should do:
2.0.0
intomaster
.=====
(we had an old plan - it's here for reference)
merge this into masterrelease 1.20.0wait for tf 0.12, revendor core libraries and etc on the 2.0.0 branch.shudder, grit our teeth, andgit fetch; git checkout tpg/2.0.0; git branch master -f; git push tpg master -f
.This will have the effect of throwing everything sinceaway. That is 100% correct - this history is wrong and as far as I know, everything after that commit is also correctly merged into2.0.0
. A ping @rileykarson to confirm that 8a62911 is correctly merged into 2.0.0.The only other commits between e64502a (the point of divergence betweenmaster
and2.0.0
) and 2f6b39e (master
, before this PR) are two reverts (which we can safely remove) and a typo fix (77a4497) which was added accidentally.