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

API for getting paths exposed for an environment #89

Open
whitlockjc opened this issue Dec 7, 2016 · 3 comments
Open

API for getting paths exposed for an environment #89

whitlockjc opened this issue Dec 7, 2016 · 3 comments

Comments

@whitlockjc
Copy link
Contributor

We need an API that will return the unique list of paths for all deployed applications within that environment. This would be a GET operation on /environments/{org}:{env}/paths and it should return a structure like this:

{
  "paths": [
    "/foo",
    "/bar"
  ]
}
@whitlockjc
Copy link
Contributor Author

Hold off on this, proposed design might render this unnecessary.

@mpnally
Copy link
Contributor

mpnally commented Dec 8, 2016

I had a slightly different idea for this. I imagined that if there is an environment whose hostName is nike-test.apigee.net, then we would support a runtime GET on https://nike-test.apigee.net/__paths__.This would be implemented by having the router generate a file containing a list of paths at the time it generates the nginx config. It would also generate a 'location' for /__paths__ that returns this file. If we wanted to have https://api.enterprise.apigee.com/v1/o/nike/environments/test/hostedTargetPaths return the same thing, that could be arranged by just forwarding the request. I don't see a motivation to have a enrober URL for this.

@jbowen93
Copy link
Contributor

@whitlockjc Is this still important? We now store hosts as the environment level but this could be implemented by getting all deployments and parsing their paths annotations.

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

No branches or pull requests

3 participants