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

[query] api: Respect env+zone headers in topic #2159

Merged
merged 8 commits into from
Feb 21, 2020

Conversation

schallert
Copy link
Collaborator

What this PR does / why we need it: We previously had not been taking the Cluster-Environment-Name and Cluster-Zone-Name headers into account in the topic handler. Users rely on these for namespace and placement handlers. This updates the topic handlers to respect them as well.

Fixes #

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?:


@schallert schallert marked this pull request as ready for review February 20, 2020 04:44
@schallert
Copy link
Collaborator Author

I've tested this in a test cluster and was able to create topics for an environment other than the one the coordinator was configured with 👍 .

Copy link
Collaborator

@robskillington robskillington left a comment

Choose a reason for hiding this comment

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

LGTM

@schallert schallert closed this Feb 20, 2020
@schallert schallert reopened this Feb 20, 2020
@schallert schallert force-pushed the schallert/topic_env_override branch 2 times, most recently from d6c9e31 to 4393859 Compare February 20, 2020 21:29
schallert and others added 5 commits February 20, 2020 17:06
We recently updated our Buildkite stack. The new version of the agents
doesn't come with netcat installed, which we use in our integration
tests. "Install" it if necessary.
@schallert schallert force-pushed the schallert/topic_env_override branch from 4393859 to 789ea4d Compare February 21, 2020 03:18
@codecov
Copy link

codecov bot commented Feb 21, 2020

Codecov Report

❗ No coverage uploaded for pull request base (master@3da5a7e). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##             master   #2159   +/-   ##
========================================
  Coverage          ?   61.4%           
========================================
  Files             ?     807           
  Lines             ?   78644           
  Branches          ?       0           
========================================
  Hits              ?   48324           
  Misses            ?   26760           
  Partials          ?    3560
Flag Coverage Δ
#aggregator 100% <ø> (?)
#cluster 100% <ø> (?)
#collector 41.8% <ø> (?)
#dbnode 100% <ø> (?)
#m3em 100% <ø> (?)
#m3ninx 100% <ø> (?)
#m3nsch 100% <ø> (?)
#metrics 100% <ø> (?)
#msg 100% <ø> (?)
#query 100% <ø> (?)
#x 100% <ø> (?)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3da5a7e...789ea4d. Read the comment docs.

commit 9f05f58
Author: Matt Schallert <[email protected]>
Date:   Thu Feb 20 21:25:25 2020 -0500

    undo debug

commit 8f8f832
Author: Matt Schallert <[email protected]>
Date:   Thu Feb 20 20:08:56 2020 -0500

    try undo addr change

commit dd83408
Author: Matt Schallert <[email protected]>
Date:   Thu Feb 20 18:27:50 2020 -0500

    another way

commit 99a2dfb
Author: Matt Schallert <[email protected]>
Date:   Thu Feb 20 17:45:21 2020 -0500

    fix ips

commit 3d90281
Author: Matt Schallert <[email protected]>
Date:   Thu Feb 20 17:35:43 2020 -0500

    fix nc addrs
@schallert schallert force-pushed the schallert/topic_env_override branch from 789ea4d to 25f8907 Compare February 21, 2020 03:19
@schallert schallert merged commit 4cd86c7 into master Feb 21, 2020
@schallert schallert deleted the schallert/topic_env_override branch February 21, 2020 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants