[query] Adding complete tags to remote server with integration test #1656
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -5,7 +5,7 @@ set -xe | |||
| # expected to be run from root of repository | |||
| cd $GOPATH/src/github.com/m3db/m3 | |||
|
|
|||
| SERVICES=(m3dbnode m3coordinator m3aggregator) | |||
| SERVICES=( m3coordinator ) | |||
There was a problem hiding this comment.
nit: Revert changes to this file? We should probably put a way to override the services to build (an env var or something).
There was a problem hiding this comment.
Oops, thought I'd reverted these changes
13 tasks
arnikola
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Fixes part of #1519 by adding remote CompleteTags endpoint with an integration test.
Special notes for your reviewer:
Does this PR introduce a user-facing and/or backwards incompatible change?:
Does this PR require updating code package or user-facing documentation?: