Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

Bind API endpoint at /fleet/v1 #983

Closed
bcwaldon opened this issue Oct 20, 2014 · 1 comment · Fixed by #1008
Closed

Bind API endpoint at /fleet/v1 #983

bcwaldon opened this issue Oct 20, 2014 · 1 comment · Fixed by #1008
Assignees
@bcwaldon
Labels
area/api kind/enhancement
Milestone
v0.9.0

Comments

@bcwaldon
Copy link
Contributor

  1. Remove the "alpha" label since the API is stable enough at this point to actually be released
  2. Future-proof the root namepace with the "fleet" prefix since we have talked about adding an agent-level API which we might want to stick at "/agent/v1"

The previous "/v1-alpha" path should remain supported.
@bcwaldon bcwaldon added this to the v0.9.0 milestone Oct 20, 2014
@bcwaldon bcwaldon mentioned this issue Oct 20, 2014
Closed
@bcwaldon
Copy link
Contributor Author

It would be great if fleetctl could figure out where the actual endpoint is based on several forms of the --endpoint argument. For example, if I had fleetd hidden behind a load balancer listening on 127.0.0.1:56928 with a virtual path "fleet", fleetctl should be able to determine the correct path to hit based on the following values of --endpoint:

  • 127.0.0.1:56928/fleet
  • 127.0.0.1:56928/fleet/cluster
  • 127.0.0.1:56928/fleet/cluster/v1

@bcwaldon bcwaldon self-assigned this Oct 21, 2014
@bcwaldon bcwaldon mentioned this issue Oct 21, 2014
Closed
@bcwaldon bcwaldon changed the title Bind API endpoint at /cluster/v1 Bind API endpoint at /fleet/v1 Oct 24, 2014
@bcwaldon bcwaldon mentioned this issue Oct 28, 2014
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bcwaldon bcwaldon

Labels
area/api kind/enhancement
Projects
None yet
Milestone
v0.9.0
Development

Successfully merging a pull request may close this issue.

Bind API at /fleet/v1 bcwaldon/fleet
1 participant
@bcwaldon