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

treat registry.consul.kvpath as prefix #417

Merged
merged 3 commits into from
Feb 2, 2018

Conversation

magiconair
Copy link
Contributor

@magiconair magiconair commented Dec 29, 2017

This patch extends the behavior of the registry.consul.kvpath
and treats it as a prefix instead of a single key. fabio will
now list the key and all available subkeys in alphabetical order
and combine them for the routing table. Each subsection will get
header which contains key name.

Fixes #396

@magiconair magiconair added this to the 1.5.6 milestone Dec 29, 2017
@magiconair magiconair modified the milestones: 1.5.6, 1.5.7 Jan 5, 2018
This patch extends the behavior of the registry.consul.kvpath
and treats it as a prefix instead of a single key. fabio will
now list the key and all available subkeys in alphabetical order
and combine them for the routing table. Each subsection will get
header which contains key name.

Todo: the ui needs to handle that as well
@magiconair magiconair force-pushed the issue-396-consul-kvpath-prefix branch from 530342e to 6738ce8 Compare February 2, 2018 11:57
@magiconair magiconair merged commit 859b573 into master Feb 2, 2018
@magiconair magiconair deleted the issue-396-consul-kvpath-prefix branch February 2, 2018 21:28
@magiconair magiconair changed the title Issue #396: treat registry.consul.kvpath as prefix treat registry.consul.kvpath as prefix Feb 2, 2018
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.

Static / Manual routes management via API
1 participant