Skip to content

Commit bf75d7b

Browse files
RoRoJbene2k1
andcommitted
Apply suggestions from code review
Co-authored-by: Benedikt Rollik <[email protected]>
1 parent 475f49c commit bf75d7b

File tree

2 files changed

+2
-3
lines changed

2 files changed

+2
-3
lines changed

network/interlink/reference-content/provisioning.mdx

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,4 +103,3 @@ Scaleway stops billing you for your InterLink immediately after step 2. Your par
103103
<Message type="note">
104104
If the provisioning of your InterLink by the partner was never completed, e.g. you a) never contacted the partner to request provisioning of the InterLink, or b) the partner refused to provision your InterLink, you do not need to contact the partner again to request that they deprovision the resource. Deleting it on the Scaleway side is sufficient.
105105
</Message>
106-

network/interlink/reference-content/statuses.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ dates:
1919
InterLink is currently in [Private Beta](https://www.scaleway.com/en/betas/), and only available to selected testers.
2020
</Message>
2121

22-
An InterLink always has a **status**, which can be retrieved via the API using the [Get a link](https://scaleway-developers-production-internal.s3-website.fr-par.internal.scaleway.com/en/developers/api/interlink/#path-links-get-a-link) call.
22+
An InterLink always has a **status**, which can be retrieved via the API using the [Get a link](https://www.scaleway.com/en/developers/api/interlink/#path-links-get-a-link) call.
2323

2424
This document explains the different statuses possible for an InterLink, and how to understand them.
2525

@@ -34,6 +34,6 @@ This document explains the different statuses possible for an InterLink, and how
3434
| **Active** | The InterLink is in a ready state, and traffic can flow. <br/><br/> The InterLink has been provisioned on both the Scaleway side and the partner side, and is now in an active state. Traffic can flow across the InterLink (presuming that allowed routes lists, route propagation, and an attached VPC are correctly configured). |
3535
| **Limited Connectivity** | The InterLink is provisioned, but IP connectivity is limited. <br/><br/> This may be the case if either, but not both of, the BGP IPv4 or IPv6 sessions are down. |
3636
| **Down / All down** | The InterLink is provisioned, but there is no IP connectivity. <br/><br/> The InterLink has been provisioned successfully on both sides, but both BGP sessions (IPv4 and IPv6) are down and traffic cannot flow. Open a support ticket with Scaleway, or contact your partner. |
37-
| **Locked** | The InterLink has been locked by the Trust and Safety team <br/><br/> You cannot carry out any actions on the InterLink. Open a support ticket.|
37+
| **Locked** | The InterLink has been locked by the Trust and Safety team <br/><br/> You cannot carry out any actions on the InterLink. Open a support ticket. |
3838
| **Deprovisioning** | Deletion of the InterLink has been initiated on either the partner side or the Scaleway side, but has not been finalized. <br/><br/> An InterLink must be deleted by both Scaleway and the partner in order to move to `Deleted` status. If you have deleted an InterLink on the Scaleway side, ensure you contact the partner separately to request that they delete the resource on their side. If you have deleted an InterLink on the partner side, ensure that you delete the resource on the Scaleway side. |
3939
| **Deleted** | The InterLink has been deprovisioned by both Scaleway and the partner, and is now deleted. |

0 commit comments

Comments
 (0)