-
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
Dataproc autogen bucket changes #1171
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.
I think that deprecation message could be much-improved by linking to the documentation in question, pointing out a workaround, or adding a next step to help users that are confused as to how to go about updating to take the deprecation into account.
google/resource_dataproc_cluster.go
Outdated
Type: schema.TypeBool, | ||
Optional: true, | ||
Default: false, | ||
Deprecated: "see documentation", |
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.
A link to the documentation here would be great.
Added more context to the deprecation message. |
* add extra wait for storage bucket object deletion * make timeout for object deletion 5 minutes, make it succeed 3 times * delete the cluster before deleting the bucket * deprecate delete_autogen_bucket * improve deprecation message
* add extra wait for storage bucket object deletion * make timeout for object deletion 5 minutes, make it succeed 3 times * delete the cluster before deleting the bucket * deprecate delete_autogen_bucket * improve deprecation message
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 PR does two things:
delete_autogen_bucket
. This shouldn't really be an option- clusters in the same region all share the same autogenerated bucket, so if we delete it then it's unclear what would happen to other dataproc clusters in that region. There's not really much harm in keeping it around, since there's only one per region.