Skip to content

Commit 4b93348

Browse files
thomas-tacquetnerda-codesRoRoJ
authored
fix(serverless): some qa on links (#4339)
* fix(serverless): some qa on links * Apply suggestions from code review Co-authored-by: Rowena Jones <[email protected]> --------- Co-authored-by: Néda <[email protected]> Co-authored-by: Rowena Jones <[email protected]>
1 parent cd77bf7 commit 4b93348

File tree

5 files changed

+11
-5
lines changed

5 files changed

+11
-5
lines changed

pages/serverless-containers/how-to/test-a-container.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ categories:
1616
This page shows you how to execute Serverless Containers from the [Scaleway console](https://console.scaleway.com). The **Test** feature of a container allows you to run your code using a selection of methods to make sure it behaves as expected.
1717

1818
<Message type="note">
19-
Testing **Private** Serverless Functions is not possible using the Scaleway console due to CORS limitations. Refer to the [dedicated documentation](/serverless-functions/how-to/create-auth-token-from-console/) for more information on how to secure and test a private function.
19+
Testing **Private** Serverless Functions is not possible using the Scaleway console due to CORS limitations. Refer to the [dedicated documentation](/serverless-containers/how-to/create-auth-token-from-console/) for more information on how to secure and test a private function.
2020
</Message>
2121

2222
<Macro id="requirements" />

pages/serverless-functions/how-to/add-trigger-to-a-function.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ You can create triggers on private functions, but to update the privacy of a fun
3939

4040
## Queue triggers
4141

42-
[Queue triggers](/serverless-containers/concepts/#queue-trigger) allow you to automatically invoke a function using events stored in a [queue](/messaging/concepts/#queue).
42+
[Queue triggers](/serverless-functions/concepts/#queue-trigger) allow you to automatically invoke a function using events stored in a [queue](/messaging/concepts/#queue).
4343

4444
Only queues created with the Scaleway Queues product are compatible with Serverless Functions.
4545

pages/serverless-functions/reference-content/deploy-function.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Many of the examples found in our [Serverless Examples repository](https://githu
4242

4343
## Terraform
4444

45-
Serverless Functions integrate easily with your infrastructure as code, via our [Terraform provider and resources](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/container).
45+
Serverless Functions integrate easily with your infrastructure as code, via our [Terraform provider and resources](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/function).
4646

4747
Examples using Terraform can be found in our [Serverless Examples repository](https://github.com/scaleway/serverless-examples), such as our [example using Terraform with Python](https://github.com/scaleway/serverless-examples/tree/main/functions/terraform-python-example).
4848

pages/serverless-jobs/concepts.mdx

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ categories:
1414

1515
## Container Registry
1616

17-
Container Registry is the place where your images are stored before being deployed. We recommend using Scaleway Container Registry for optimal integration. See the [migration guide](/serverless-containers/api-cli/migrate-external-image-to-scaleway-registry/) for full details.
17+
Container Registry is the place where your images are stored before being deployed. We recommend using Scaleway Container Registry for optimal integration. See the [migration guide](/serverless-jobs/api-cli/migrate-external-image-to-scaleway-registry/) for full details.
1818

1919
## Environment variables
2020

@@ -100,6 +100,12 @@ This means that each request is treated as a new and isolated event, and there i
100100

101101
To store data you can use [Scaleway Object Storage](/object-storage/), [Scaleway Managed Databases](/managed-databases-for-postgresql-and-mysql/), and [Scaleway Serverless Databases](/serverless-sql-databases/).
102102

103+
## Terraform
104+
105+
Terraform is an infrastructure-as-code tool, owned by Hashicorp. Serverless Jobs integrate easily with your infrastructure as code, via our [Terraform provider and resources](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/job_definition).
106+
107+
Examples using Terraform can be found in our [Serverless Examples repository](https://github.com/scaleway/serverless-examples), such as our [example using Terraform with Serverless Jobs](https://github.com/scaleway/serverless-examples/blob/main/jobs/terraform-hello-world).
108+
103109
## vCPU-s
104110

105111
Unit used to measure the resource consumption of a container. It reflects the amount of vCPU used over time.

pages/serverless-jobs/quickstart.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Scaleway Serverless Jobs allows you to run recurring tasks in the cloud. A [Job]
1818

1919
Jobs are designed for autonomous and recurring tasks, and therefore do not offer automatic scaling or a web interface.
2020

21-
Refer to the [differences between Jobs, Containers, and Functions](/serverless-containers/reference-content/difference-jobs-functions-containers/) for more information on Scaleway's different Serverless products.
21+
Refer to the [differences between Jobs, Containers, and Functions](/serverless-jobs/reference-content/difference-jobs-functions-containers/) for more information on Scaleway's different Serverless products.
2222

2323
This page explains how to create a job definition with the latest Alpine Linux image, how to execute it, and delete it.
2424

0 commit comments

Comments
 (0)