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

Do not apply kopia retention policy on kando location push #2442

Merged
merged 1 commit into from
Oct 27, 2023

Conversation

pavannd1
Copy link
Contributor

Change Overview

  • With kopia v0.14.1, repository clients are not allowed to apply retention policy during snapshot creation without appropriate permissions/ACLs. This causes the clients to hit a 403 error.
  • This PR temporarily removes the retention part.
  • We should explore the right ACLs for repository server users and re-enable the retention. Created [FEAT] Apply retention policy directly from kopia for kando location push #2441 for tracking.

Pull request type

Please check the type of change your PR introduces:

  • 🚧 Work in Progress
  • 🌈 Refactoring (no functional changes, no api changes)
  • 🐹 Trivial/Minor
  • 🐛 Bugfix
  • 🌻 Feature
  • 🗺️ Documentation
  • 🤖 Test

Issues

  • fixes #issue-number

Test Plan

  • 💪 Manual
  • ⚡ Unit test
  • 💚 E2E

@mergify mergify bot merged commit 878a4c7 into master Oct 27, 2023
15 checks passed
@mergify mergify bot deleted the remove-kopia-retention-kando branch October 27, 2023 06:17
Comment on lines +71 to +74
// _, err = policy.ApplyRetentionPolicy(ctx, rep, sourceInfo, true)
// if err != nil {
// return "", 0, errors.Wrap(err, "Failed to apply kopia retention policy")
// }
Copy link
Contributor

Choose a reason for hiding this comment

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

Should commented code be removed, and instead be replaced with a description?

Not sure whether issue #2441 already has a link to this PR / commit. If not, this comment should create the link anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants