map-route options documentation is wrong

Inizia dalla pagina di documentazione di map-route e dalla pagina di documentazione di supporting-http2 collegate nell’issue, quindi confronta i relativi nomi dei flag con l’output dell’help di cf map-route mostrato qui. Aggiorna l’opzione documentata in modo che corrisponda alla CLI e verifica che entrambe le pagine descrivano lo stesso comando e lo stesso comportamento HTTP/2.

• I reviewed open and closed github issues that may be related to my problem.
• I tried updating to the latest version of the CF CLI to see if it fixed my problem.
• I attempted to run the command with CF_TRACE=1 to help debug the issue.
• I am reporting a bug that others will be able to reproduce.

Describe the bug and the command you saw an issue with
I wanted to set a route using cf map-routewith HTTP/2 enabled like it is described in the documentation.

What happened
An error occurred Incorrect Usage: unknown flag destination-protocol'. The help command for map-route` gave me those instructions:

NAME:
   map-route - Map a route to an app

USAGE:
   Map an HTTP route:
      cf map-route APP_NAME DOMAIN [--hostname HOSTNAME] [--path PATH] [--app-protocol PROTOCOL] [--option OPTION=VALUE]
   
   Map a TCP route:
      cf map-route APP_NAME DOMAIN [--port PORT] [--option OPTION=VALUE]

EXAMPLES:
   cf map-route my-app example.com                                                      # example.com
   cf map-route my-app example.com --hostname myhost                                    # myhost.example.com
   cf map-route my-app example.com --hostname myhost -o loadbalancing=least-connection  # myhost.example.com with a per-route option
   cf map-route my-app example.com --hostname myhost --path foo                         # myhost.example.com/foo
   cf map-route my-app example.com --hostname myhost --app-protocol http2               # myhost.example.com
   cf map-route my-app example.com --port 5000                                          # example.com:5000

OPTIONS:
   --hostname, -n      Hostname for the HTTP route (required for shared domains)
   --path              Path for the HTTP route
   --port              Port for the TCP route (default: random port)
   --app-protocol      [Beta flag, subject to change] Protocol for the route destination (default: http1). Only applied to HTTP routes
   --option, -o        Set the value of a per-route option

SEE ALSO:
   create-route, routes, unmap-route, update-route

I then tried using app-protocol instead which fixed the problem so no current blocker.

Expected behavior
I expect the cli help and the documentation to be aligned and that the description in the documentation is correct. Please correct the documentation.

Exact Steps To Reproduce
Steps to reproduce the behavior; include the exact CLI commands and verbose output:

1. Run cf map-route <YOUR_APP> <YOUR_DOMAIN> --destination-protocol http2
2. See error

Provide more context

• Same error on this documentation page

Notes regarding V6 and V7 CLI support:

• V6:
  • Minimum supported version of CF Deployment: v7.0.0 (CAPI Release: 1.74.0 (APIs 2.128.0 and 3.63.0))
  • Maximum supported version of CF Deployment: v13.4.0 (CAPI Release: 1.94.0 (APIs 2.149.0 and 3.84.0))
• V7:
  • Minimum supported version of CF Deployment: v13.5.0 (CAPI Release: 1.95.0 (APIs 2.150.0 and 3.85.0))