-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Job revert command and API endpoint can take a string version tag name #24059
Job revert command and API endpoint can take a string version tag name #24059
Conversation
api/jobs.go
Outdated
@@ -531,7 +531,7 @@ func (j *Jobs) Dispatch(jobID string, meta map[string]string, | |||
// Revert is used to revert the given job to the passed version. If | |||
// enforceVersion is set, the job is only reverted if the current version is at | |||
// the passed version. | |||
func (j *Jobs) Revert(jobID string, version uint64, enforcePriorVersion *uint64, | |||
func (j *Jobs) Revert(jobID string, version *uint64, versionTag *string, enforcePriorVersion *uint64, |
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.
version becomes optional, and therefore now a pointer.
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.
We can't change the signature of api
package methods. We'll need a new Revert
-like method to do this.
Better yet, we can do what we did on the Tag/Untag Versions PR and query for the version for a given tag in the CLI/UI and then leave this unchanged.
671ae9b
to
d186b13
Compare
2c59fa7
to
81b3e44
Compare
d186b13
to
b1255f0
Compare
bb3a3dc
to
04dbb05
Compare
04dbb05
to
697348f
Compare
64a38dc
to
69dfec6
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.
LGTM!
@@ -270,6 +270,23 @@ func (j *Jobs) Versions(jobID string, diffs bool, q *QueryOptions) ([]*Job, []*J | |||
return j.VersionsOpts(jobID, opts, q) | |||
} | |||
|
|||
// VersionByTag is used to retrieve a job version by its TaggedVersion name. |
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.
Nice little helper! Mirrors what we needed in the state store. 👍
// Clear out the TaggedVersion to prevent tag duplication | ||
revJob.TaggedVersion = nil |
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.
Oof, good catch!
69dfec6
to
97bb6da
Compare
* TaggedVersion information in structs, rather than job_endpoint (#23841) * TaggedVersion information in structs, rather than job_endpoint * Test for taggedVersion description length * Some API plumbing * Tag and Untag job versions (#23863) * Tag and Untag at API level on down, but am I unblocking the wrong thing? * Code and comment cleanup * Unset methods generally now I stare long into the namespace abyss * Namespace passes through with QueryOptions removed from a write requesting struct * Comment and PR review cleanup * Version back to VersionStr * Generally consolidate unset logic into apply for version tagging * Addressed some PR comments * Auth check and RPC forwarding * uint64 instead of pointer for job version after api layer and renamed copy * job tag command split into apply and unset * latest-version convenience handling moved to CLI command level * CLI tests for tagging/untagging * UI parts removed * Add to job table when unsetting job tag on latest version * Vestigial no more * Compare versions by name and version number with the nomad history command (#23889) * First pass at passing a tagname and/or diff version to plan/versions requests * versions API now takes compare_to flags * Job history command output can have tag names and descriptions * compare_to to diff-tag and diff-version, plus adding flags to history command * 0th version now shows a diff if a specific diff target is requested * Addressing some PR comments * Simplify the diff-appending part of jobVersions and hide None-type diffs from CLI * Remove the diff-tag and diff-version parts of nomad job plan, with an eye toward making them a new top-level CLI command soon * Version diff tests * re-implement JobVersionByTagName * Test mods and simplification * Documentation for nomad job history additions * Prevent pruning and reaping of TaggedVersion jobs (#23983) tagged versions should not count against JobTrackedVersions i.e. new job versions being inserted should not evict tagged versions and GC should not delete a job if any of its versions are tagged Co-authored-by: Daniel Bennett <[email protected]> --------- Co-authored-by: Daniel Bennett <[email protected]> * [ui] Version Tags on the job versions page (#24013) * Timeline styles and their buttons modernized, and tags added * styled but not yet functional version blocks * Rough pass at edit/unedit UX * Styles consolidated * better UX around version tag crud, plus adapter and serializers * Mirage and acceptance tests * Modify percy to not show time-based things --------- Co-authored-by: Daniel Bennett <[email protected]> * Job revert command and API endpoint can take a string version tag name (#24059) * Job revert command and API endpoint can take a string version tag name * RevertOpts as a signature-modified alternative to Revert() * job revert CLI test * Version pointers in endpoint tests * Dont copy over the tag when a job is reverted to a version with a tag * Convert tag name to version number at CLI level * Client method for version lookup by tag * No longer double-declaring client * [ui] Add tag filter to the job versions page (#24064) * Rough pass at the UI for version diff dropdown * Cleanup and diff fetching via adapter method * TaggedVersion now VersionTag (#24066) --------- Co-authored-by: Daniel Bennett <[email protected]>
Allows the second argument on
nomad job revert
to be the string name of a job version tagFixes an issue where reverting (either by number or by tag name) to an older job version with a tag, duplicated that tag on the newly-run version.
(This is not desirable for, among other reasons, a same-tag-name situation making
tag unset
unreliable)Resolves #24053