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

Don't move velero v1 plugins to new proto dir #5263

Merged
merged 1 commit into from
Sep 15, 2022

Conversation

sseago
Copy link
Collaborator

@sseago sseago commented Aug 30, 2022

Signed-off-by: Scott Seago [email protected]

Thank you for contributing to Velero!

To preserve backwards compatibility, don't move velero
v1 plugins to new proto dir.

Does your change fix a particular issue?

Fixes #5262

Please indicate you've done the following:

  • [x ] Accepted the DCO. Commits without the DCO will delay acceptance.
  • [x ] Created a changelog file or added /kind changelog-not-required as a comment on this pull request.
  • Updated the corresponding documentation in site/content/docs/main.

@reasonerjt
Copy link
Contributor

reasonerjt commented Sep 5, 2022

@sseago thanks for the fix!

I think this change is a good improvement, could you please also update the section in the design https://github.com/vmware-tanzu/velero/blob/main/design/plugin-versioning.md#proto-service-definitions, to clarify that for backward compatibility the v1 files will be remained in pkg/plugin/proto/<plugin_kind>/

To preserve backwards compatibility, don't move velero
v1 plugins to new proto dir.

Signed-off-by: Scott Seago <[email protected]>
@sseago
Copy link
Collaborator Author

sseago commented Sep 5, 2022

@reasonerjt doc updated with the change.

@weshayutin
Copy link
Contributor

Looks good, thanks for putting this up

@shubham-pampattiwar
Copy link
Collaborator

Important fix, lets get this in.

@shubham-pampattiwar shubham-pampattiwar merged commit 1e138af into vmware-tanzu:main Sep 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BackupItemAction refactoring for plugin versioning isn't backwards compatible
5 participants