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

Add prioritized resource list for backups #586

Closed
ncdc opened this issue Jun 25, 2018 · 5 comments
Closed

Add prioritized resource list for backups #586

ncdc opened this issue Jun 25, 2018 · 5 comments
Labels
Candidate for close Issues that should be closed and need a team review before closing Enhancement/User End-User Enhancement to Velero

Comments

@ncdc
Copy link
Contributor

ncdc commented Jun 25, 2018

Similar to restores, backups should be able to process resources in a well-defined order.

@ncdc ncdc added P1 - Important Enhancement/User End-User Enhancement to Velero labels Jun 25, 2018
@ncdc ncdc added this to the v1.0.0 milestone Jun 25, 2018
@ncdc ncdc mentioned this issue Aug 8, 2018
@ncdc ncdc modified the milestones: v1.0.0, v1.x Nov 27, 2018
@dymurray
Copy link
Contributor

Is there some documentation around how to prioritize resources on restore?

@dymurray
Copy link
Contributor

dymurray commented Mar 14, 2019

I see the default list, but It's not obvious to me how to extend this to support custom resources.

https://github.com/heptio/velero/blob/4583aa707821f5860b09b67cc091b70d504e1385/pkg/cmd/server/server.go#L440

If this is currently unsupported, is there anyway we could expose this to the end user? If not we could certainly carry a different default list in a fork.

@ncdc
Copy link
Contributor Author

ncdc commented Mar 15, 2019

@dymurray
Copy link
Contributor

Awesome, thank you @ncdc!

@skriss skriss added the Candidate for close Issues that should be closed and need a team review before closing label Sep 10, 2019
@skriss
Copy link
Contributor

skriss commented Sep 19, 2019

Thanks for this request. We are not currently prioritizing this item within our roadmap, and as such will be closing out the issue. Please feel free to reach out as needed in this issue or a new one.

@skriss skriss closed this as completed Sep 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Candidate for close Issues that should be closed and need a team review before closing Enhancement/User End-User Enhancement to Velero
Projects
None yet
Development

No branches or pull requests

3 participants