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(default_retention_period): Changes to backup.copy API to support the default retention period feature #1874

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

satyaprakashg
Copy link

With the default retention period feature, null value for expiration time is a valid value.
If the expiration time is not specified (null) at the time of copy backup then the
source backup expiration time will be used for expiring the destination backup as well.

In this commit: expireTime is already optional in CopyBackupOptions and no changes are
required to handle the case of missing expireTime in CopyBackupOptions. Adding unit-tests
for copy backup for the current scenario and a few other scenarios (since they seem to
be missing).

…rt the default retention period feature

With the default retention period feature, null value for expiration time is a valid value. If the
expiration time is not specified (null) at the time of create backup then the backup will be
retained for the duration of maximum retention period.

In this commit, expireTime is made optional in CreateBackupOptions and backup.create API
is fixed to handle the null value in the CreateBackupOptions.
… the default retention period feature

With the default retention period feature, null value for expiration time is a valid value.
If the expiration time is not specified (null) at the time of copy backup then the
source backup expiration time will be used for expiring the destination backup as well.

In this commit: expireTime is already optional in CopyBackupOptions and no changes are
required to handle the case of missing expireTime in CopyBackupOptions. Adding unit-tests
for copy backup for the current scenario and a few other scenarios (since they seem to
be missing).
@satyaprakashg satyaprakashg requested review from a team as code owners July 4, 2023 09:06
@product-auto-label product-auto-label bot added size: m Pull request size is medium. api: spanner Issues related to the googleapis/nodejs-spanner API. labels Jul 4, 2023
@satyaprakashg
Copy link
Author

@surbhigarg92 Could you please review this diff. Also, please add "do not merge" tag on this diff since the backend changes are not merged yet.

@surbhigarg92 surbhigarg92 added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Jul 5, 2023
test/backup.ts Show resolved Hide resolved
test/backup.ts Outdated Show resolved Hide resolved
test/backup.ts Outdated Show resolved Hide resolved
test/backup.ts Outdated Show resolved Hide resolved
… the default retention period feature

With the default retention period feature, null value for expiration time is a valid value.
If the expiration time is not specified (null) at the time of copy backup then the
source backup expiration time will be used for expiring the destination backup as well.

In this commit: expireTime is already optional in CopyBackupOptions and no changes are
required to handle the case of missing expireTime in CopyBackupOptions. Adding unit-tests
for copy backup for the current scenario and a few other scenarios (since they seem to
be missing).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: spanner Issues related to the googleapis/nodejs-spanner API. do not merge Indicates a pull request not ready for merge, due to either quality or timing. size: m Pull request size is medium.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants