feat(backup): surface incrementalBaseBackupId on backup status and list - #477
Closed
OsamaAnsar wants to merge 1 commit into
Closed
OsamaAnsar wants to merge 1 commit into
OsamaAnsar wants to merge 1 commit into
Conversation
Contributor
Author
|
I agree with the CLA |
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
| Infrastructure as Code | View in Orca | ||
| SAST | View in Orca | ||
| Secrets | View in Orca | ||
| Vulnerabilities | View in Orca |
|
To avoid any confusion in the future about your contribution to Weaviate, we work with a Contributor License Agreement. If you agree, you can simply add a comment to this PR that you agree with the CLA so that we can merge. |
Contributor
|
Duplicate of: #459 |
Contributor
Author
|
Closing in favor of #459 which covers this more broadly — thanks for the heads up @dudanogueira. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #441.
Exposes
incrementalBaseBackupIdonBackupStatusReturn— the ID of the base backup a file-based incremental backup was built on (empty/absent when the backup is not incremental). Mirrors weaviate-python-client#2116.The field is already in the vendored OpenAPI spec (
incremental_base_backup_idonBackupCreateStatusResponseandBackupListResponse); it just wasn't mapped through to the public types.Changes
src/openapi/types.ts— exportBackupListResponsesrc/collections/backup/types.ts—incrementalBaseBackupId?: stringonBackupStatusReturn(inherited byBackupReturn)src/collections/backup/client.ts—parseStatusmaps it from the create-status response;backup.list()maps it from each list entry (other list-response quirks left untouched)test/collections/backup/mock.test.ts— mock the list + create-status endpoints returningincremental_base_backup_id; 2 tests asserting it surfaces (and staysundefinedfor a non-incremental backup)Testing
npx tsc --noEmit,eslint,prettier --checkclean.test/collections/backup/mock.test.tspasses (8/8, including the 2 new).