feat: add support for restore token#2548
Conversation
Merge branch 'googleapis:main' into support-for-restore-token
| name: string; | ||
|
|
||
| generation?: number; | ||
| restoreToken?: string; |
There was a problem hiding this comment.
Is there a reason to have this field as both a class level and metadata level field?
There was a problem hiding this comment.
I've noticed that in some scenarios, a refresh token is associated with a specific generation ID. To ensure consistent behavior and avoid potential issues, I've implemented the refresh token handling in a way that aligns with the generation ID concept. This approach will help maintain data integrity and security.
|
My understanding is that the restore token would be returned on a call to delete. Is that going to be a separate PR or should it be included here? |
I'm currently focused on implementing support for restore tokens in the get, list, and restore operations. |
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #restoreToken