James Rasell 751c8217d1 core: allow setting and propagation of eval priority on job de/registration (#11532) ... This change modifies the Nomad job register and deregister RPCs to accept an updated option set which includes eval priority. This param is optional and override the use of the job priority to set the eval priority. In order to ensure all evaluations as a result of the request use the same eval priority, the priority is shared to the allocReconciler and deploymentWatcher. This creates a new distinction between eval priority and job priority. The Nomad agent HTTP API has been modified to allow setting the eval priority on job update and delete. To keep consistency with the current v1 API, job update accepts this as a payload param; job delete accepts this as a query param. Any user supplied value is validated within the agent HTTP handler removing the need to pass invalid requests to the server. The register and deregister opts functions now all for setting the eval priority on requests. The change includes a small change to the DeregisterOpts function which handles nil opts. This brings the function inline with the RegisterOpts.		2021-11-23 09:23:31 +01:00
..
inputs	core: allow setting and propagation of eval priority on job de/registration (#11532)	2021-11-23 09:23:31 +01:00
eval_priority.go	core: allow setting and propagation of eval priority on job de/registration (#11532)	2021-11-23 09:23:31 +01:00