### Name

`kf unmap-route` - Revoke an Apps's access to receive traffic from the Route

### Synopsis

```
kf unmap-route APP_NAME DOMAIN [--hostname HOSTNAME] [--path PATH] [flags]
```

### Description

Unmapping an App from a Route will cause traffic matching the Route to no longer be forwarded to the App.

The App may still receive traffic from an unmapped Route for a small period of time while the traffic rules on the gateways are propagated.

The Route will re-balance its routing weights so other Apps mapped to it will receive the traffic. If no other Apps are bound the Route will return a 404 HTTP status code.

### Examples

```
  # Unmap myapp.example.com from myapp in the targeted Space
  kf unmap-route myapp example.com --hostname myapp
  
  # Unmap the Route in a specific Space
  kf unmap-route --space myspace myapp example.com --hostname myapp
  
  # Unmap a Route with a path
  kf unmap-route myapp example.com --hostname myapp --path /mypath
```

### Flags

`--async`
:   Don't wait for the action to complete on the server before returning

`--destination-port=int32`
:   Port on the App the route will connect to

`-h, --help`
:   help for unmap-route

`--hostname=string`
:   Hostname for the route

`--path=string`
:   URL Path for the route

### Inherited flags

These flags are inherited from parent commands.

`--config=string`
:   Config file (default is $HOME/.kf)

`--kubeconfig=string`
:   Kubectl config file (default is $HOME/.kube/config)

`--log-http`
:   Log HTTP requests to stderr

`--space=string`
:   Space to run the command against. This overrides the currently targeted space