test-all-usage-edge-services-route-rules-add-usage.golden

🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
Add route rules to an existing route stage, specified by its `route_stage_id`.

USAGE:
  scw edge-services route-rules add <route-stage-id ...> [arg=value ...]

ARGS:
  route-stage-id                                                       ID of the route stage to update
  [route-rules.{index}.rule-http-match.method-filters.{index}]         HTTP methods to filter for. A request using any of these methods will be considered to match the rule. Possible values are `get`, `post`, `put`, `patch`, `delete`, `head`, `options`. All methods will match if none is provided (unknown_method_filter | get | post | put | patch | delete | head | options)
  [route-rules.{index}.rule-http-match.path-filter.path-filter-type]   Type of filter to match for the HTTP URL path. For now, all path filters must be written in regex and use the `regex` type (unknown_path_filter | regex)
  [route-rules.{index}.rule-http-match.path-filter.value]              Value to be matched for the HTTP URL path
  [route-rules.{index}.backend-stage-id]                               ID of the backend stage that requests matching the rule should be forwarded to
  [route-rules.{index}.waf-stage-id]                                   ID of the WAF stage that requests matching the rule should be forwarded to
  [after-position]                                                     Add rules after the given position
  [before-position]                                                    Add rules before the given position

FLAGS:
  -h, --help                help for add
      --list-sub-commands   List all subcommands

GLOBAL FLAGS:
  -c, --config string    The path to the config file
  -D, --debug            Enable debug mode
  -o, --output string    Output format: json or human, see 'scw help output' for more info (default "human")
  -p, --profile string   The config profile to use