-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
ephemeral resource grpc wrappers #35784
Changes from all commits
9899d59
eb184a5
9468767
6f5007e
2408c4a
0c5fae9
c875174
51f1c5f
170e846
5a7a113
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. drive-by comment 🚗: There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. thanks, I seemed to have somehow rebased that back in 😵 |
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 will match the provider side with the new field/naming once this gets merged 👍🏻
For the removal of
is_closable
, is the plan forClose
to be called for all ephemeral resources regardless of if they were renewed/not renewed?Additionally, will returned diagnostics from
Close
stop execution or will they behave more like theStop
RPC for providers and just log?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.
Yeah, Close would always be called. Making
Close
a defined part of the lifecycle regardless of whether it does anything or not makes the implementations much simpler, and since the plugin has to implement the calls anyway, it would have to at least be a noop regardless of whether it's called.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 yeah, and diagnostics from
Close
would only be able to pass on some info to the user, and make Terraform exit with an error. TheClose
has to happen after all dependencies have used the value, so if there were an error there are no more operations to stop execution of.