Skip to content
This repository has been archived by the owner on Oct 11, 2024. It is now read-only.

retain kopia-assist when not on incrementals #1941

Merged
merged 4 commits into from
Dec 23, 2022
Merged

Conversation

ryanfkeepers
Copy link
Contributor

Description

Adds a flag to the BackupCollections interface
that identifies whether the caller is running an
incremental backup or not. If they are, kopia
will utilize the previous base snapshots when
building the directory tree.

Does this PR need a docs update or release note?

  • ⛔ No

Type of change

  • 🌻 Feature

Issue(s)

Test Plan

  • 💚 E2E

@ryanfkeepers ryanfkeepers requested a review from ashmrtn December 23, 2022 19:21
@ryanfkeepers ryanfkeepers self-assigned this Dec 23, 2022
@@ -80,6 +81,7 @@ func (ss *streamStore) WriteBackupDetails(
ss.service,
nil,
nil,
isIncremental,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this depends on how much of the underlying incremental behavior we want to expose to higher layer. For now since we're already passing nil for the set of bases I think it's fine to just hardcode it to false and not even expose it as another parameter

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, I was looking at the wrong param. You're right, no point in the flag if the input is nil.

Adds a flag to the BackupCollections interface
that identifies whether the caller is running an
incremental backup or not.  If they are, kopia
will utilize the previous base snapshots when
building the directory tree.
@ryanfkeepers ryanfkeepers temporarily deployed to Testing December 23, 2022 19:31 — with GitHub Actions Inactive
@ryanfkeepers ryanfkeepers temporarily deployed to Testing December 23, 2022 19:31 — with GitHub Actions Inactive
@ryanfkeepers ryanfkeepers temporarily deployed to Testing December 23, 2022 19:31 — with GitHub Actions Inactive
@ryanfkeepers ryanfkeepers temporarily deployed to Testing December 23, 2022 19:33 — with GitHub Actions Inactive
@ryanfkeepers ryanfkeepers temporarily deployed to Testing December 23, 2022 19:33 — with GitHub Actions Inactive
@ryanfkeepers ryanfkeepers temporarily deployed to Testing December 23, 2022 19:33 — with GitHub Actions Inactive
@aviator-app
Copy link
Contributor

aviator-app bot commented Dec 23, 2022

Aviator status

Aviator will automatically update this comment as the status of the PR changes.

This PR was merged using Aviator.

@ryanfkeepers ryanfkeepers temporarily deployed to Testing December 23, 2022 19:34 — with GitHub Actions Inactive
@ryanfkeepers ryanfkeepers temporarily deployed to Testing December 23, 2022 19:34 — with GitHub Actions Inactive
@ryanfkeepers ryanfkeepers temporarily deployed to Testing December 23, 2022 19:34 — with GitHub Actions Inactive
@aviator-app aviator-app bot temporarily deployed to Testing December 23, 2022 19:57 Inactive
@aviator-app aviator-app bot temporarily deployed to Testing December 23, 2022 19:57 Inactive
@aviator-app aviator-app bot temporarily deployed to Testing December 23, 2022 19:58 Inactive
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@aviator-app aviator-app bot temporarily deployed to Testing December 23, 2022 19:58 Inactive
@aviator-app aviator-app bot temporarily deployed to Testing December 23, 2022 19:58 Inactive
@aviator-app aviator-app bot temporarily deployed to Testing December 23, 2022 19:58 Inactive
@aviator-app aviator-app bot merged commit 9e9cb43 into main Dec 23, 2022
@aviator-app aviator-app bot deleted the issue-1901-split-base branch December 23, 2022 20:14
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants