-
Notifications
You must be signed in to change notification settings - Fork 9
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
Writable snapshot support #92
Conversation
) (string, error) { | ||
// PAPI call: POST https://1.2.3.4:8080/platform/1/quota/quotas | ||
// { "enforced" : true, | ||
// "include_snapshots" : false, | ||
// "include_snapshots" : true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
better to retain the current behavior unless it is really required. Snapshot doesn't consume much space- maybe a few bytes for the metadata, and the size is not directly related to the source volume size.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Writable snaphots could diverge. I do agree that we probably should not include snapshots but this is in goscaleio so the work is already done to expose this so let the applications decide on the business rules. Does not hurt to keep it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although by exposing this we break compatibility. Terraform uses this module as well.
Closing PR for now as the solution for the GitHub issue is under discussion. |
PR Submission checklist
PR adds support for the basic APIs for managing writable snapshots.
GitHub Issues
List the GitHub issues impacted by this PR:
Common PR Checklist:
Description of your changes:
Added the basic Get/List/Create/Delete functions for managing writable snapshots.