Re: Soliciting feedback on a UX change for route services
i personally don't like specifying the space in the "cf create-route"toggle quoted message Show quoted text
command because it's one of the only cli commands i can think of that
requires specifying the space explicitly rather than using the currently
targeted space. i believe we should consider changing that now since a
single argument could be interpreted as the DOMAIN and the space could be
an explicit option parameter.
regarding the UX, i have tried some explicit examples with
cf create-service audit-service free-plan my-audit-service
this seems fine, it means create a service that is expected to have a
route-service endpoint the attributes, similar to a syslog drain service
cf update-route foo example.com -s my-audit-service
we don't have "cf update-route" today. is the reason to make the
service_instance a parameter to account for more route options in the
future? what about a "naked domain" that does not have a hostname like
example.com? this cli pattern above does not really allow for that right?
perhaps it's better to have a similar syntax to the existing route commands:
cf update-route example.com -n foo -s my-audit-service
what about supplying an external URL that is not a service on the platform?
would we do that with a user provided service instance or an explicit URL
added to the route?
# using a service
cf create-route development example.com -n foo -s my-audit-service
# using an external URL
cf create-route development example.com -n foo -u https://audit.example.com
how would we remove a route-service from a route, by using a particular
option that means remove any route-service on the route?
cf update-route example.com -n foo -r
On Tue, Jun 23, 2015 at 9:14 PM, Benjamin Black <bblack(a)pivotal.io> wrote:
yes, this is how it should work.