You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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"
]
}
The text was updated successfully, but these errors were encountered:
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.
@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.
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:The text was updated successfully, but these errors were encountered: