You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: cmd/scw/testdata/test-all-usage-lbacl-create-usage.golden
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ARGS:
10
10
name=<generated> ACL name
11
11
[action.type] Action to take when incoming traffic matches an ACL filter (allow | deny | redirect)
12
12
[action.redirect.type] Redirect type (location | scheme)
13
-
[action.redirect.target] Redirect target. For a location redirect, you can use a URL e.g. `https://scaleway.com`. Using a scheme name (e.g. `https`, `http`, `ftp`, `git`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `location` redirect to preserve parts of the original request in the redirection URL are {{ host }}, {{ query }}, {{ path }} and {{ scheme }}
13
+
[action.redirect.target] Redirect target. For a location redirect, you can use a URL e.g. `https://scaleway.com`. Using a scheme name (e.g. `https`, `http`, `ftp`, `git`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `location` redirect to preserve parts of the original request in the redirection URL are \{\{ host \}\}, \{\{ query \}\}, \{\{ path \}\} and \{\{ scheme \}\}
14
14
[action.redirect.code] HTTP redirect code to use. Valid values are 301, 302, 303, 307 and 308. Default value is 302
15
15
[match.ip-subnet.{index}] List of IPs or CIDR v4/v6 addresses to filter for from the client side
16
16
[match.http-filter] Type of HTTP filter to match. Extracts the request's URL path, which starts at the first slash and ends before the question mark (without the host part). Defines where to filter for the http_filter_value. Only supported for HTTP backends (acl_http_filter_none | path_begin | path_end | regex | http_header_match)
Copy file name to clipboardExpand all lines: cmd/scw/testdata/test-all-usage-lbacl-set-usage.golden
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ARGS:
9
9
acls.{index}.name ACL name
10
10
[acls.{index}.action.type] Action to take when incoming traffic matches an ACL filter (allow | deny | redirect)
11
11
[acls.{index}.action.redirect.type] Redirect type (location | scheme)
12
-
[acls.{index}.action.redirect.target] Redirect target. For a location redirect, you can use a URL e.g. `https://scaleway.com`. Using a scheme name (e.g. `https`, `http`, `ftp`, `git`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `location` redirect to preserve parts of the original request in the redirection URL are {{ host }}, {{ query }}, {{ path }} and {{ scheme }}
12
+
[acls.{index}.action.redirect.target] Redirect target. For a location redirect, you can use a URL e.g. `https://scaleway.com`. Using a scheme name (e.g. `https`, `http`, `ftp`, `git`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `location` redirect to preserve parts of the original request in the redirection URL are \{\{ host \}\}, \{\{ query \}\}, \{\{ path \}\} and \{\{ scheme \}\}
13
13
[acls.{index}.action.redirect.code] HTTP redirect code to use. Valid values are 301, 302, 303, 307 and 308. Default value is 302
14
14
[acls.{index}.match.ip-subnet.{index}] List of IPs or CIDR v4/v6 addresses to filter for from the client side
15
15
[acls.{index}.match.http-filter] Type of HTTP filter to match. Extracts the request's URL path, which starts at the first slash and ends before the question mark (without the host part). Defines where to filter for the http_filter_value. Only supported for HTTP backends (acl_http_filter_none | path_begin | path_end | regex | http_header_match)
Copy file name to clipboardExpand all lines: cmd/scw/testdata/test-all-usage-lbacl-update-usage.golden
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ARGS:
10
10
name ACL name
11
11
[action.type] Action to take when incoming traffic matches an ACL filter (allow | deny | redirect)
12
12
[action.redirect.type] Redirect type (location | scheme)
13
-
[action.redirect.target] Redirect target. For a location redirect, you can use a URL e.g. `https://scaleway.com`. Using a scheme name (e.g. `https`, `http`, `ftp`, `git`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `location` redirect to preserve parts of the original request in the redirection URL are {{ host }}, {{ query }}, {{ path }} and {{ scheme }}
13
+
[action.redirect.target] Redirect target. For a location redirect, you can use a URL e.g. `https://scaleway.com`. Using a scheme name (e.g. `https`, `http`, `ftp`, `git`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `location` redirect to preserve parts of the original request in the redirection URL are \{\{ host \}\}, \{\{ query \}\}, \{\{ path \}\} and \{\{ scheme \}\}
14
14
[action.redirect.code] HTTP redirect code to use. Valid values are 301, 302, 303, 307 and 308. Default value is 302
15
15
[match.ip-subnet.{index}] List of IPs or CIDR v4/v6 addresses to filter for from the client side
16
16
[match.http-filter] Type of HTTP filter to match. Extracts the request's URL path, which starts at the first slash and ends before the question mark (without the host part). Defines where to filter for the http_filter_value. Only supported for HTTP backends (acl_http_filter_none | path_begin | path_end | regex | http_header_match)
Copy file name to clipboardExpand all lines: cmd/scw/testdata/test-all-usage-lblb-create-usage.golden
-1Lines changed: 0 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,6 @@ ARGS:
11
11
[description] Description for the Load Balancer
12
12
[assign-flexible-ip] Defines whether to automatically assign a flexible public IP to lb. Default value is `false` (do not assign).
13
13
[ip-ids.{index}] List of IP IDs to attach to the Load Balancer
14
-
[assign-flexible-ip] Defines whether to automatically assign a flexible public IP to lb. Default value is `false` (do not assign).
15
14
[tags.{index}] List of tags for the Load Balancer
16
15
[type=LB-S] Load Balancer commercial offer type. Use the Load Balancer types endpoint to retrieve a list of available offer types (LB-S | LB-GP-M | LB-GP-L)
17
16
[ssl-compatibility-level] Determines the minimal SSL version which needs to be supported on the client side, in an SSL/TLS offloading context. Intermediate is suitable for general-purpose servers with a variety of clients, recommended for almost all systems. Modern is suitable for services with clients that support TLS 1.3 and do not need backward compatibility. Old is compatible with a small number of very old clients and should be used only as a last resort (ssl_compatibility_level_unknown | ssl_compatibility_level_intermediate | ssl_compatibility_level_modern | ssl_compatibility_level_old)
| name | Required<br />Default: `<generated>`| ACL name |
94
94
| action.type | One of: `allow`, `deny`, `redirect`| Action to take when incoming traffic matches an ACL filter |
95
95
| action.redirect.type | One of: `location`, `scheme`| Redirect type |
96
-
| action.redirect.target || Redirect target. For a location redirect, you can use a URL e.g. `https://scaleway.com`. Using a scheme name (e.g. `https`, `http`, `ftp`, `git`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `location` redirect to preserve parts of the original request in the redirection URL are {{ host }}, {{ query }}, {{ path }} and {{ scheme }} |
96
+
| action.redirect.target || Redirect target. For a location redirect, you can use a URL e.g. `https://scaleway.com`. Using a scheme name (e.g. `https`, `http`, `ftp`, `git`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `location` redirect to preserve parts of the original request in the redirection URL are \{\{ host \}\}, \{\{ query \}\}, \{\{ path \}\} and \{\{ scheme \}\}|
97
97
| action.redirect.code || HTTP redirect code to use. Valid values are 301, 302, 303, 307 and 308. Default value is 302 |
98
98
| match.ip-subnet.{index} || List of IPs or CIDR v4/v6 addresses to filter for from the client side |
99
99
| match.http-filter | One of: `acl_http_filter_none`, `path_begin`, `path_end`, `regex`, `http_header_match`| Type of HTTP filter to match. Extracts the request's URL path, which starts at the first slash and ends before the question mark (without the host part). Defines where to filter for the http_filter_value. Only supported for HTTP backends |
@@ -186,7 +186,7 @@ scw lb acl set [arg=value ...]
186
186
| acls.{index}.name | Required | ACL name |
187
187
| acls.{index}.action.type | One of: `allow`, `deny`, `redirect`| Action to take when incoming traffic matches an ACL filter |
188
188
| acls.{index}.action.redirect.type | One of: `location`, `scheme`| Redirect type |
189
-
| acls.{index}.action.redirect.target || Redirect target. For a location redirect, you can use a URL e.g. `https://scaleway.com`. Using a scheme name (e.g. `https`, `http`, `ftp`, `git`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `location` redirect to preserve parts of the original request in the redirection URL are {{ host }}, {{ query }}, {{ path }} and {{ scheme }} |
189
+
| acls.{index}.action.redirect.target || Redirect target. For a location redirect, you can use a URL e.g. `https://scaleway.com`. Using a scheme name (e.g. `https`, `http`, `ftp`, `git`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `location` redirect to preserve parts of the original request in the redirection URL are \{\{ host \}\}, \{\{ query \}\}, \{\{ path \}\} and \{\{ scheme \}\}|
190
190
| acls.{index}.action.redirect.code || HTTP redirect code to use. Valid values are 301, 302, 303, 307 and 308. Default value is 302 |
191
191
| acls.{index}.match.ip-subnet.{index} || List of IPs or CIDR v4/v6 addresses to filter for from the client side |
192
192
| acls.{index}.match.http-filter | One of: `acl_http_filter_none`, `path_begin`, `path_end`, `regex`, `http_header_match`| Type of HTTP filter to match. Extracts the request's URL path, which starts at the first slash and ends before the question mark (without the host part). Defines where to filter for the http_filter_value. Only supported for HTTP backends |
| action.type | One of: `allow`, `deny`, `redirect`| Action to take when incoming traffic matches an ACL filter |
221
221
| action.redirect.type | One of: `location`, `scheme`| Redirect type |
222
-
| action.redirect.target || Redirect target. For a location redirect, you can use a URL e.g. `https://scaleway.com`. Using a scheme name (e.g. `https`, `http`, `ftp`, `git`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `location` redirect to preserve parts of the original request in the redirection URL are {{ host }}, {{ query }}, {{ path }} and {{ scheme }} |
222
+
| action.redirect.target || Redirect target. For a location redirect, you can use a URL e.g. `https://scaleway.com`. Using a scheme name (e.g. `https`, `http`, `ftp`, `git`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `location` redirect to preserve parts of the original request in the redirection URL are \{\{ host \}\}, \{\{ query \}\}, \{\{ path \}\} and \{\{ scheme \}\}|
223
223
| action.redirect.code || HTTP redirect code to use. Valid values are 301, 302, 303, 307 and 308. Default value is 302 |
224
224
| match.ip-subnet.{index} || List of IPs or CIDR v4/v6 addresses to filter for from the client side |
225
225
| match.http-filter | One of: `acl_http_filter_none`, `path_begin`, `path_end`, `regex`, `http_header_match`| Type of HTTP filter to match. Extracts the request's URL path, which starts at the first slash and ends before the question mark (without the host part). Defines where to filter for the http_filter_value. Only supported for HTTP backends |
|~~ip-id~~| Deprecated | ID of an existing flexible IP address to attach to the Load Balancer |
904
904
| assign-flexible-ip || Defines whether to automatically assign a flexible public IP to lb. Default value is `false` (do not assign). |
905
905
| ip-ids.{index} || List of IP IDs to attach to the Load Balancer |
906
-
| assign-flexible-ip || Defines whether to automatically assign a flexible public IP to lb. Default value is `false` (do not assign). |
907
906
| tags.{index} || List of tags for the Load Balancer |
908
907
| type | Default: `LB-S`<br />One of: `LB-S`, `LB-GP-M`, `LB-GP-L`| Load Balancer commercial offer type. Use the Load Balancer types endpoint to retrieve a list of available offer types |
909
908
| ssl-compatibility-level | One of: `ssl_compatibility_level_unknown`, `ssl_compatibility_level_intermediate`, `ssl_compatibility_level_modern`, `ssl_compatibility_level_old`| Determines the minimal SSL version which needs to be supported on the client side, in an SSL/TLS offloading context. Intermediate is suitable for general-purpose servers with a variety of clients, recommended for almost all systems. Modern is suitable for services with clients that support TLS 1.3 and do not need backward compatibility. Old is compatible with a small number of very old clients and should be used only as a last resort |
Short: `Redirect target. For a location redirect, you can use a URL e.g. `+"`"+`https://scaleway.com`+"`"+`. Using a scheme name (e.g. `+"`"+`https`+"`"+`, `+"`"+`http`+"`"+`, `+"`"+`ftp`+"`"+`, `+"`"+`git`+"`"+`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `+"`"+`location`+"`"+` redirect to preserve parts of the original request in the redirection URL are {{ host }}, {{ query }}, {{ path }} and {{ scheme }}`,
2199
+
Short: `Redirect target. For a location redirect, you can use a URL e.g. `+"`"+`https://scaleway.com`+"`"+`. Using a scheme name (e.g. `+"`"+`https`+"`"+`, `+"`"+`http`+"`"+`, `+"`"+`ftp`+"`"+`, `+"`"+`git`+"`"+`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `+"`"+`location`+"`"+` redirect to preserve parts of the original request in the redirection URL are \{\{ host \}\}, \{\{ query \}\}, \{\{ path \}\} and \{\{ scheme \}\}`,
Short: `Redirect target. For a location redirect, you can use a URL e.g. `+"`"+`https://scaleway.com`+"`"+`. Using a scheme name (e.g. `+"`"+`https`+"`"+`, `+"`"+`http`+"`"+`, `+"`"+`ftp`+"`"+`, `+"`"+`git`+"`"+`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `+"`"+`location`+"`"+` redirect to preserve parts of the original request in the redirection URL are {{ host }}, {{ query }}, {{ path }} and {{ scheme }}`,
2346
+
Short: `Redirect target. For a location redirect, you can use a URL e.g. `+"`"+`https://scaleway.com`+"`"+`. Using a scheme name (e.g. `+"`"+`https`+"`"+`, `+"`"+`http`+"`"+`, `+"`"+`ftp`+"`"+`, `+"`"+`git`+"`"+`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `+"`"+`location`+"`"+` redirect to preserve parts of the original request in the redirection URL are \{\{ host \}\}, \{\{ query \}\}, \{\{ path \}\} and \{\{ scheme \}\}`,
Short: `Redirect target. For a location redirect, you can use a URL e.g. `+"`"+`https://scaleway.com`+"`"+`. Using a scheme name (e.g. `+"`"+`https`+"`"+`, `+"`"+`http`+"`"+`, `+"`"+`ftp`+"`"+`, `+"`"+`git`+"`"+`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `+"`"+`location`+"`"+` redirect to preserve parts of the original request in the redirection URL are {{ host }}, {{ query }}, {{ path }} and {{ scheme }}`,
2492
+
Short: `Redirect target. For a location redirect, you can use a URL e.g. `+"`"+`https://scaleway.com`+"`"+`. Using a scheme name (e.g. `+"`"+`https`+"`"+`, `+"`"+`http`+"`"+`, `+"`"+`ftp`+"`"+`, `+"`"+`git`+"`"+`) will replace the request's original scheme. This can be useful to implement HTTP to HTTPS redirects. Valid placeholders that can be used in a `+"`"+`location`+"`"+` redirect to preserve parts of the original request in the redirection URL are \{\{ host \}\}, \{\{ query \}\}, \{\{ path \}\} and \{\{ scheme \}\}`,
0 commit comments