-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Catalog Register: Generate UUID for services registered without one #4294
Conversation
This makes the behavior line up with the docs and expected behavior
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.
Just a couple formatting questions but looks good otherwise.
agent/catalog_endpoint_test.go
Outdated
"github.com/hashicorp/consul/testutil/retry" | ||
"github.com/hashicorp/serf/coordinate" | ||
"github.com/stretchr/testify/assert" | ||
"github.com/stretchr/testify/require" |
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.
Nit: Is this an artifact of the GitHub diff viewer or are these not tabbed/formatted properly?
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.
Right you are, looks like something happened to my editor plugin to run go fmt on save.
agent/consul/catalog_endpoint.go
Outdated
return fmt.Errorf("Failed to generate ID: %v", err) | ||
} | ||
|
||
args.ID = types.NodeID(id) |
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.
Same question here, is this formatted properly (go fmt
)?
Oh follow up question: should the default UUID test actually go in |
@mitchellh There are actually two catalog_endpoint_test.go files. Looks like I dropped it in the wrong one. |
08e3bbd
to
0f70034
Compare
Fixes #4249
This makes the behavior line up with the docs and expected behavior