Allow setting of submission metadata.
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
Currently the deployment descriptions as output in the command `nomad deployment list` are defined as constants in the Nomad [structs](https://github.com/hashicorp/nomad/blob/master/nomad/structs/structs.go#L4091) package. It would be nice if an operator can optionally set a custom description for deployments; allowing the Nomad tracking of deployments to become more personalised. This could be particularly helpful on clusters with numerous customers and for dashboarding.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the deployment description definitions in nomad/structs/structs.go and trace how the `nomad deployment list` command obtains and displays them. Determine where an operator-provided description should enter the deployment metadata flow. Done means deployments can optionally carry a custom description and `nomad deployment list` displays it for tracking and dashboarding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100