Skip to content
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

Pass service metadata "external-source" for consul UI integration #4889

Merged
merged 1 commit into from
Nov 16, 2018

Conversation

preetapan
Copy link
Contributor

This lets the Consul UI show a little Nomad logo on services that Nomad registers.

nomad_source

@preetapan preetapan requested a review from schmichael November 16, 2018 17:41
Copy link
Member

@nickethier nickethier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!!

@preetapan preetapan merged commit 5003f51 into master Nov 16, 2018
@preetapan preetapan deleted the f-service-meta branch November 16, 2018 18:24
@@ -566,6 +566,10 @@ func (c *ServiceClient) RegisterAgent(role string, services []*structs.Service)
Tags: service.Tags,
Address: host,
Port: port,
// This enables the consul UI to show that Nomad registered this service
Meta: map[string]string{
"external-source": "nomad",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@preetapan would it be possible to have the nomad alloc ID in this meta key set as well? would be some of my work 1000x easier at work when trying to map nomad service{} to consul service id outside of nomad

@github-actions
Copy link

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.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 16, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants