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

[service][health-check] Execute health-check rule from root path #1078

Closed
brasseld opened this Issue Feb 13, 2018 · 0 comments

Comments

Projects
None yet
2 participants
@brasseld
Member

brasseld commented Feb 13, 2018

We have an endpoint declared with url https://api.gravitee.io/echo/api
We want check health status from https://api.gravitee.io/echo/health

Currently, there is no way to call such URL.

@brasseld brasseld added this to the 1.14.0 milestone Feb 13, 2018

@brasseld brasseld self-assigned this Feb 13, 2018

brasseld added a commit to gravitee-io/gravitee-definition that referenced this issue Feb 19, 2018

brasseld added a commit to gravitee-io/gravitee-gateway that referenced this issue Feb 19, 2018

brasseld added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Feb 19, 2018

brasseld added a commit to gravitee-io/gravitee-management-webui that referenced this issue Feb 19, 2018

@aelamrani aelamrani changed the title from [service] [health-check] Execute health-check rule from root path to [service][health-check] Execute health-check rule from root path Feb 21, 2018

brasseld added a commit to gravitee-io/gravitee-definition that referenced this issue Feb 27, 2018

NicolasGeraud added a commit to gravitee-io/gravitee-management-webui that referenced this issue Feb 27, 2018

aelamrani added a commit to gravitee-io/gravitee-gateway that referenced this issue Feb 27, 2018

aelamrani added a commit to gravitee-io/gravitee-definition that referenced this issue Feb 27, 2018

aelamrani added a commit to gravitee-io/gravitee-gateway that referenced this issue Feb 27, 2018

aelamrani added a commit to gravitee-io/gravitee-management-webui that referenced this issue Feb 27, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment