-
Notifications
You must be signed in to change notification settings - Fork 2
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
optional expire flags + automated versioning #30
Conversation
c1edaee
to
43c7571
Compare
/retest |
4110035
to
a6af040
Compare
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.
Approving from the functionality perspective, it works great AFAICT.
/hold |
a6af040
to
67d6078
Compare
/unhold |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: bkabrda, fghanmi, SequeI The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Adding expiry values to all metadata files when using tuftool update is now optional, a user can just supply a variation of any he wants and the pre-existing expiry values that were not specified with a flag will be passed on to the new version.
Versioning has been removed from the users hands, now it will automatically calculate a new version removing the issue of overwriting pre existing metadata files and adding general QoL. A --force-version flag exists to forcefully change the version of a specific metadata file.