-
Notifications
You must be signed in to change notification settings - Fork 22
Open
Description
The links structure in the Rancher API is invaluable. Without it many common tasks are impossible.
For example, given a Service ID, getting a list of its instances/containers is nearly impossible with the SDK as it stands, but if one could access the links.instances property it would be easy.
Example links container in a Service response:
links": {
"self": "…/v1/projects/1a5/services/1s153",
"account": "…/v1/projects/1a5/services/1s153/account",
"consumedbyservices": "…/v1/projects/1a5/services/1s153/consumedbyservices",
"consumedservices": "…/v1/projects/1a5/services/1s153/consumedservices",
"environment": "…/v1/projects/1a5/services/1s153/environment",
"instances": "…/v1/projects/1a5/services/1s153/instances",
"serviceExposeMaps": "…/v1/projects/1a5/services/1s153/serviceexposemaps",
"containerStats": "…/v1/projects/1a5/services/1s153/containerstats",
},Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels