Skip to content

Commit 4335e7e

Browse files
Laure-diyfodil
andauthored
feat(edge-services): add support v1alpha1 (scaleway#3908)
Co-authored-by: Yacine FODIL <[email protected]>
1 parent 4bd82de commit 4335e7e

File tree

40 files changed

+2838
-0
lines changed

40 files changed

+2838
-0
lines changed
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
Create a new backend stage. You must specify either a `scaleway_s3` (for a Scaleway Object Storage bucket) or `scaleway_lb` (for a Scaleway Load Balancer) field to configure the origin.
4+
5+
USAGE:
6+
scw edge-services backend-stage create [arg=value ...]
7+
8+
ARGS:
9+
[project-id] Project ID to use. If none is passed the default project ID will be used
10+
[scaleway-s3.bucket-name] Name of the Bucket
11+
[scaleway-s3.bucket-region] Region of the Bucket
12+
[scaleway-s3.is-website] Defines whether the bucket website feature is enabled
13+
[scaleway-lb.lbs.{index}.id] ID of the Load Balancer
14+
[scaleway-lb.lbs.{index}.zone] Zone of the Load Balancer
15+
[scaleway-lb.lbs.{index}.frontend-id] ID of the frontend linked to the Load Balancer
16+
[scaleway-lb.lbs.{index}.is-ssl] Defines whether the Load Balancer's frontend handles SSL connections
17+
[scaleway-lb.lbs.{index}.domain-name] Fully Qualified Domain Name (in the format subdomain.example.com) to use in HTTP requests sent towards your Load Balancer
18+
19+
FLAGS:
20+
-h, --help help for create
21+
22+
GLOBAL FLAGS:
23+
-c, --config string The path to the config file
24+
-D, --debug Enable debug mode
25+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
26+
-p, --profile string The config profile to use
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
Delete an existing backend stage, specified by its `backend_stage_id`. Deleting a backend stage is permanent, and cannot be undone.
4+
5+
USAGE:
6+
scw edge-services backend-stage delete <backend-stage-id ...> [arg=value ...]
7+
8+
ARGS:
9+
backend-stage-id ID of the backend stage to delete
10+
11+
FLAGS:
12+
-h, --help help for delete
13+
14+
GLOBAL FLAGS:
15+
-c, --config string The path to the config file
16+
-D, --debug Enable debug mode
17+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
18+
-p, --profile string The config profile to use
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
Retrieve information about an existing backend stage, specified by its `backend_stage_id`. Its full details, including `scaleway_s3` or `scaleway_lb`, are returned in the response object.
4+
5+
USAGE:
6+
scw edge-services backend-stage get <backend-stage-id ...> [arg=value ...]
7+
8+
ARGS:
9+
backend-stage-id ID of the requested backend stage
10+
11+
FLAGS:
12+
-h, --help help for get
13+
14+
GLOBAL FLAGS:
15+
-c, --config string The path to the config file
16+
-D, --debug Enable debug mode
17+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
18+
-p, --profile string The config profile to use
Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
List all backend stages, for a Scaleway Organization or Scaleway Project. By default, the backend stages returned in the list are ordered by creation date in ascending order, though this can be modified via the `order_by` field.
4+
5+
USAGE:
6+
scw edge-services backend-stage list [arg=value ...]
7+
8+
ARGS:
9+
[order-by] Sort order of backend stages in the response (created_at_asc | created_at_desc)
10+
[pipeline-id] Pipeline ID to filter for, only backend stages from this pipeline will be returned
11+
[project-id] Project ID to filter for, only backend stages from this Project will be returned
12+
[bucket-name] Bucket name to filter for, only backend stages from this Bucket will be returned
13+
[bucket-region] Bucket region to filter for, only backend stages with buckets in this region will be returned
14+
15+
FLAGS:
16+
-h, --help help for list
17+
18+
GLOBAL FLAGS:
19+
-c, --config string The path to the config file
20+
-D, --debug Enable debug mode
21+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
22+
-p, --profile string The config profile to use
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
Update the parameters of an existing backend stage, specified by its `backend_stage_id`.
4+
5+
USAGE:
6+
scw edge-services backend-stage update <backend-stage-id ...> [arg=value ...]
7+
8+
ARGS:
9+
backend-stage-id ID of the backend stage to update
10+
[scaleway-s3.bucket-name] Name of the Bucket
11+
[scaleway-s3.bucket-region] Region of the Bucket
12+
[scaleway-s3.is-website] Defines whether the bucket website feature is enabled
13+
[scaleway-lb.lbs.{index}.id] ID of the Load Balancer
14+
[scaleway-lb.lbs.{index}.zone] Zone of the Load Balancer
15+
[scaleway-lb.lbs.{index}.frontend-id] ID of the frontend linked to the Load Balancer
16+
[scaleway-lb.lbs.{index}.is-ssl] Defines whether the Load Balancer's frontend handles SSL connections
17+
[scaleway-lb.lbs.{index}.domain-name] Fully Qualified Domain Name (in the format subdomain.example.com) to use in HTTP requests sent towards your Load Balancer
18+
19+
FLAGS:
20+
-h, --help help for update
21+
22+
GLOBAL FLAGS:
23+
-c, --config string The path to the config file
24+
-D, --debug Enable debug mode
25+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
26+
-p, --profile string The config profile to use
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
Backend-stage management commands.
4+
5+
USAGE:
6+
scw edge-services backend-stage <command>
7+
8+
AVAILABLE COMMANDS:
9+
create Create backend stage
10+
delete Delete backend stage
11+
get Get backend stage
12+
list List backend stages
13+
update Update backend stage
14+
15+
FLAGS:
16+
-h, --help help for backend-stage
17+
18+
GLOBAL FLAGS:
19+
-c, --config string The path to the config file
20+
-D, --debug Enable debug mode
21+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
22+
-p, --profile string The config profile to use
23+
24+
Use "scw edge-services backend-stage [command] --help" for more information about a command.
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
Create a new cache stage. You must specify the `fallback_ttl` field to customize the TTL of the cache.
4+
5+
USAGE:
6+
scw edge-services cache-stage create [arg=value ...]
7+
8+
ARGS:
9+
[project-id] Project ID to use. If none is passed the default project ID will be used
10+
[fallback-ttl=3600s] Time To Live (TTL) in seconds. Defines how long content is cached
11+
[backend-stage-id] Backend stage ID the cache stage will be linked to
12+
13+
FLAGS:
14+
-h, --help help for create
15+
16+
GLOBAL FLAGS:
17+
-c, --config string The path to the config file
18+
-D, --debug Enable debug mode
19+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
20+
-p, --profile string The config profile to use
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
Delete an existing cache stage, specified by its `cache_stage_id`. Deleting a cache stage is permanent, and cannot be undone.
4+
5+
USAGE:
6+
scw edge-services cache-stage delete <cache-stage-id ...> [arg=value ...]
7+
8+
ARGS:
9+
cache-stage-id ID of the cache stage to delete
10+
11+
FLAGS:
12+
-h, --help help for delete
13+
14+
GLOBAL FLAGS:
15+
-c, --config string The path to the config file
16+
-D, --debug Enable debug mode
17+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
18+
-p, --profile string The config profile to use
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
Retrieve information about an existing cache stage, specified by its `cache_stage_id`. Its full details, including Time To Live (TTL), are returned in the response object.
4+
5+
USAGE:
6+
scw edge-services cache-stage get <cache-stage-id ...> [arg=value ...]
7+
8+
ARGS:
9+
cache-stage-id ID of the requested cache stage
10+
11+
FLAGS:
12+
-h, --help help for get
13+
14+
GLOBAL FLAGS:
15+
-c, --config string The path to the config file
16+
-D, --debug Enable debug mode
17+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
18+
-p, --profile string The config profile to use
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
List all cache stages, for a Scaleway Organization or Scaleway Project. By default, the cache stages returned in the list are ordered by creation date in ascending order, though this can be modified via the `order_by` field.
4+
5+
USAGE:
6+
scw edge-services cache-stage list [arg=value ...]
7+
8+
ARGS:
9+
[order-by] Sort order of cache stages in the response (created_at_asc | created_at_desc)
10+
[pipeline-id] Pipeline ID to filter for, only cache stages from this pipeline will be returned
11+
[project-id] Project ID to filter for, only cache stages from this Project will be returned
12+
13+
FLAGS:
14+
-h, --help help for list
15+
16+
GLOBAL FLAGS:
17+
-c, --config string The path to the config file
18+
-D, --debug Enable debug mode
19+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
20+
-p, --profile string The config profile to use
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
Update the parameters of an existing cache stage, specified by its `cache_stage_id`. Parameters which can be updated include the `fallback_ttl` and `backend_stage_id`.
4+
5+
USAGE:
6+
scw edge-services cache-stage update <cache-stage-id ...> [arg=value ...]
7+
8+
ARGS:
9+
cache-stage-id ID of the cache stage to update
10+
[fallback-ttl] Time To Live (TTL) in seconds. Defines how long content is cached
11+
[backend-stage-id] Backend stage ID the cache stage will be linked to
12+
13+
FLAGS:
14+
-h, --help help for update
15+
16+
GLOBAL FLAGS:
17+
-c, --config string The path to the config file
18+
-D, --debug Enable debug mode
19+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
20+
-p, --profile string The config profile to use
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
Cache-stage management commands.
4+
5+
USAGE:
6+
scw edge-services cache-stage <command>
7+
8+
AVAILABLE COMMANDS:
9+
create Create cache stage
10+
delete Delete cache stage
11+
get Get cache stage
12+
list List cache stages
13+
update Update cache stage
14+
15+
FLAGS:
16+
-h, --help help for cache-stage
17+
18+
GLOBAL FLAGS:
19+
-c, --config string The path to the config file
20+
-D, --debug Enable debug mode
21+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
22+
-p, --profile string The config profile to use
23+
24+
Use "scw edge-services cache-stage [command] --help" for more information about a command.
Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
Create a new DNS stage. You must specify the `fqdns` field to customize the domain endpoint, using a domain you already own.
4+
5+
USAGE:
6+
scw edge-services dns-stage create [arg=value ...]
7+
8+
ARGS:
9+
[project-id] Project ID to use. If none is passed the default project ID will be used
10+
[fqdns.{index}] Fully Qualified Domain Name (in the format subdomain.example.com) to attach to the stage
11+
[tls-stage-id] TLS stage ID the DNS stage will be linked to
12+
[cache-stage-id] Cache stage ID the DNS stage will be linked to
13+
[backend-stage-id] Backend stage ID the DNS stage will be linked to
14+
15+
FLAGS:
16+
-h, --help help for create
17+
18+
GLOBAL FLAGS:
19+
-c, --config string The path to the config file
20+
-D, --debug Enable debug mode
21+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
22+
-p, --profile string The config profile to use
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
Delete an existing DNS stage, specified by its `dns_stage_id`. Deleting a DNS stage is permanent, and cannot be undone.
4+
5+
USAGE:
6+
scw edge-services dns-stage delete <dns-stage-id ...> [arg=value ...]
7+
8+
ARGS:
9+
dns-stage-id ID of the DNS stage to delete
10+
11+
FLAGS:
12+
-h, --help help for delete
13+
14+
GLOBAL FLAGS:
15+
-c, --config string The path to the config file
16+
-D, --debug Enable debug mode
17+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
18+
-p, --profile string The config profile to use
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
Retrieve information about an existing DNS stage, specified by its `dns_stage_id`. Its full details, including FQDNs, are returned in the response object.
4+
5+
USAGE:
6+
scw edge-services dns-stage get <dns-stage-id ...> [arg=value ...]
7+
8+
ARGS:
9+
dns-stage-id ID of the requested DNS stage
10+
11+
FLAGS:
12+
-h, --help help for get
13+
14+
GLOBAL FLAGS:
15+
-c, --config string The path to the config file
16+
-D, --debug Enable debug mode
17+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
18+
-p, --profile string The config profile to use
Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
List all DNS stages, for a Scaleway Organization or Scaleway Project. By default, the DNS stages returned in the list are ordered by creation date in ascending order, though this can be modified via the `order_by` field.
4+
5+
USAGE:
6+
scw edge-services dns-stage list [arg=value ...]
7+
8+
ARGS:
9+
[order-by] Sort order of DNS stages in the response (created_at_asc | created_at_desc)
10+
[pipeline-id] Pipeline ID to filter for, only DNS stages from this pipeline will be returned
11+
[project-id] Project ID to filter for, only DNS stages from this Project will be returned
12+
[fqdn] Fully Qualified Domain Name to filter for (in the format subdomain.example.com), only DNS stages with this FQDN will be returned
13+
14+
FLAGS:
15+
-h, --help help for list
16+
17+
GLOBAL FLAGS:
18+
-c, --config string The path to the config file
19+
-D, --debug Enable debug mode
20+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
21+
-p, --profile string The config profile to use
Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
Update the parameters of an existing DNS stage, specified by its `dns_stage_id`.
4+
5+
USAGE:
6+
scw edge-services dns-stage update <dns-stage-id ...> [arg=value ...]
7+
8+
ARGS:
9+
dns-stage-id ID of the DNS stage to update
10+
[fqdns.{index}] Fully Qualified Domain Name (in the format subdomain.example.com) attached to the stage
11+
[tls-stage-id] TLS stage ID the DNS stage will be linked to
12+
[cache-stage-id] Cache stage ID the DNS stage will be linked to
13+
[backend-stage-id] Backend stage ID the DNS stage will be linked to
14+
15+
FLAGS:
16+
-h, --help help for update
17+
18+
GLOBAL FLAGS:
19+
-c, --config string The path to the config file
20+
-D, --debug Enable debug mode
21+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
22+
-p, --profile string The config profile to use
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
🎲🎲🎲 EXIT CODE: 0 🎲🎲🎲
2+
🟥🟥🟥 STDERR️️ 🟥🟥🟥️
3+
DNS-stage management commands.
4+
5+
USAGE:
6+
scw edge-services dns-stage <command>
7+
8+
AVAILABLE COMMANDS:
9+
create Create DNS stage
10+
delete Delete DNS stage
11+
get Get DNS stage
12+
list List DNS stages
13+
update Update DNS stage
14+
15+
FLAGS:
16+
-h, --help help for dns-stage
17+
18+
GLOBAL FLAGS:
19+
-c, --config string The path to the config file
20+
-D, --debug Enable debug mode
21+
-o, --output string Output format: json or human, see 'scw help output' for more info (default "human")
22+
-p, --profile string The config profile to use
23+
24+
Use "scw edge-services dns-stage [command] --help" for more information about a command.

0 commit comments

Comments
 (0)