-
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
Implemented interpolation of Job, Task group and Task Names in Service Name #509
Conversation
@@ -28,6 +28,9 @@ func (j *Job) Register(args *structs.JobRegisterRequest, reply *structs.JobRegis | |||
if err := args.Job.Validate(); err != nil { | |||
return err | |||
} | |||
|
|||
args.Job.ExpandAllServiceNames() |
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.
I would put a comment on this
LGTM Might be worth updating the nomad init output to the new name specification so people can see it |
Implemented interpolation of Job, Task group and Task Names in Service Name
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
Fixes #499
This PR disables addition of the prefix
${job-name}-${task-group}-${task}
to every Service Name. Users can add${JOB}
,${TASKGROUP}
,${TASK}
and${BASE}
to the service name and Nomad interpolates their appropriate values.