The cf-release templates allow for a "system_domain" (
https://github.com/cloudfoundry/cf-release/blob/master/templates/cf-jobs.yml#L616),
this allows for a separate namespace for non-app hostnames("app_domain").
Hope this helps

Thanks,


Jim

On Thu, Oct 8, 2015 at 2:49 AM Sylvain Gibier <sylvain(a)munichconsulting.de>
wrote:

Hi,

Bug ?

Pushing an application using a manifest.yml file with an host entry set to
'api', you are able to override the default route api.<<mycf.domain>> with
the application - preventing further cf commands to work correctly, as it
redirects traffic to new application.
I would have expect an error indicating the api.<<mycf.domain>> is already
used to prevent anyone to override api, uaa and login endpoint with a
custom app. Or am I missing something?

Is it a way - to make application/host like api, uaa, login ... not been
able to be overrided by custom application binding?

Sylvain