Skip to content

Commit 99a432a

Browse files
Apply suggestions from code review
Co-authored-by: ldecarvalho-doc <[email protected]>
1 parent 85ad328 commit 99a432a

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

pages/public-gateways/faq.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Pre-existing static leases created via the Public Gateway were fully migrated an
3333

3434
Read our [dedicated documentation](/public-gateways/reference-content/understanding-v2/) to learn how to put your gateway into IPAM-mode and replicate static DHCP reservation functionality with Scaleway IPAM.
3535

36-
## Why is my Public Gateway labelled as Legacy?
36+
## Why is my Public Gateway labeled as Legacy?
3737

3838
**Legacy** Public Gateways use a [workaround](/vpc/reference-content/vpc-migration/#public-gateways-and-vpc) to ensure compatibility with Scaleway's IPAM (**I** **P** **A**ddress **M**anagement) tool. IPAM acts as a single source of truth for the IP addresses of Scaleway resources
3939

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
meta:
33
title: Public Gateways - Additional Content
4-
description: Explore detailed Scaleway configurations, best practices and troubleshooting for Scaleway Public Gateways. Optimize configuration of your gateway with our comprehensive reference guides.
4+
description: Explore detailed Scaleway configurations, best practices and troubleshooting for Scaleway Public Gateways. Optimize the configuration of your gateway with our comprehensive reference guides.
55
content:
66
h1: Public Gateways - Additional Content
7-
paragraph: Explore detailed Scaleway configurations, best practices and troubleshooting for Scaleway Public Gateways. Optimize configuration of your gateway with our comprehensive reference guides.
7+
paragraph: Explore detailed Scaleway configurations, best practices and troubleshooting for Scaleway Public Gateways. Optimize the configuration of your gateway with our comprehensive reference guides.
88
---

pages/public-gateways/reference-content/understanding-v2.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -150,17 +150,17 @@ Allowed IPs is a new functionality of the Public Gateways API v2, that will also
150150

151151
### How do I know if I have to take action?
152152

153-
- Consider whether you mange your Public Gateway uniquely via the Scaleway console, or via calls to the API/devtools in code and scripts:
153+
- Consider whether you manage your Public Gateway uniquely via the Scaleway console, or via calls to the API/devtools in code and scripts:
154154

155155
- **Code and scripts**: If you have any code or scripts that call v1 of the API, or use devtool functionality that is removed from v2 such as DHCP object or entries, **you must take action before 1 Oct 2025**. Update your code and scripts so they point to v2 of the API. [Follow the examples provided for tools such as Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md) to rewrite your devtool templates so they do not refer to removed functionalities. Do this in synchronization with moving your gateway to IPAM mode (if necessary).
156156

157157
- **Console-only**: You do not need to take any action, except ensuring that your gateway is in IPAM mode.
158158

159159
- Check in the [Scaleway console](https://console.scaleway.com/public-gateway/public-gateways) whether your Public Gateway is in IPAM mode or legacy mode:
160160

161-
- **Legacy mode**: you must move the gateway to IPAM mode. Only IPAM mode gateways are compatible with v2. Use the **Move to IPAM mode** button in the console, the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateways-put-a-public-gateway-in-ipam-mode), or the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md).
161+
- **Legacy mode**: You must move the gateway to IPAM mode. Only IPAM mode gateways are compatible with v2. Use the **Move to IPAM mode** button in the console, the [dedicated API call](https://www.scaleway.com/en/developers/api/public-gateway/v1/#path-gateways-put-a-public-gateway-in-ipam-mode), or the `move_to_ipam` flag in [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/guides/migration_guide_vpcgw_v2.md).
162162

163-
- **IPAM mode**: you do not have any action to take, except updating any code and scripts that you have (see above).
163+
- **IPAM mode**: You do not have any action to take, except updating any code and scripts that you have (see above).
164164

165165
### How do I move my legacy Public Gateway to IPAM mode?
166166

0 commit comments

Comments
 (0)