/usr/bin/protoc-gen-grpc-gateway

Usage of /usr/bin/protoc-gen-grpc-gateway:
  -allow_delete_body
    	unless set, HTTP DELETE methods may not have a body
  -allow_patch_feature
    	determines whether to use PATCH feature involving update masks (using google.protobuf.FieldMask). (default true)
  -allow_repeated_fields_in_body body
    	allows to use repeated field in body and `response_body` field of `google.api.http` annotation option. DEPRECATED: the value is ignored and always behaves as `true`. (default true)
  -generate_unbound_methods
    	generate proxy methods even for RPC methods that have no HttpRule annotation
  -grpc_api_configuration string
    	path to gRPC API Configuration in YAML format
  -logtostderr
    	Legacy glog compatibility. This flag is a no-op, you can safely remove it
  -omit_package_doc
    	if true, no package comment will be included in the generated code
  -register_func_suffix string
    	used to construct names of generated Register*<Suffix> methods. (default "Handler")
  -repeated_path_param_separator csv
    	configures how repeated fields should be split. Allowed values are csv, `pipes`, `ssv` and `tsv`. (default "csv")
  -request_context
    	determine whether to use http.Request's context or not (default true)
  -standalone
    	generates a standalone gateway package, which imports the target service package
  -strict_deep_wildcard
    	if true, a deep wildcard (**) preceded by a segment must match at least one path segment, e.g. /v1/files/{path=**} no longer matches /v1/files
  -use_opaque_api
    	generate code compatible with the new Opaque API instead of the older Open Struct API
  -version
    	print the current version
  -warn_on_unbound_methods
    	emit a warning message if an RPC method has no HttpRule annotation