From 9c95d3c517c5f1cc58a60e96a4f92cd50dfbdf37 Mon Sep 17 00:00:00 2001 From: VEEREPALLI SHANMUKH Date: Sat, 27 Jun 2026 12:40:24 +0530 Subject: [PATCH] docs: fix broken external links in documentation --- docs/install.md | 2 +- docs/operational-procedures.md | 4 ++-- docs/operational-procedures/reserved-list-management.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/install.md b/docs/install.md index d46468b8166..b2e2b3eaf0e 100644 --- a/docs/install.md +++ b/docs/install.md @@ -158,4 +158,4 @@ Deployment of the Beam pipelines to Cloud Dataflow in the testing environments ``` Pipeline deployment in other environments are through CloudBuild. Please refer -to the [release folder](http://github.com/google/nomulus/release) for details. +to the [release folder](https://github.com/google/nomulus/releases) for details. diff --git a/docs/operational-procedures.md b/docs/operational-procedures.md index 27e613e8b38..1123b0699b1 100644 --- a/docs/operational-procedures.md +++ b/docs/operational-procedures.md @@ -43,14 +43,14 @@ metrics monitored are as follows: described by TLD, reserved list name, and the reservation type found. Follow the guide to -[set up a Stackdriver account](https://cloud.google.com/monitoring/accounts/guide) +[set up a Cloud Monitoring workspace](https://cloud.google.com/monitoring/docs) and associate it with the GCP project containing the Nomulus app. Once the two have been linked, monitoring will start automatically. For now, because the visualization of custom metrics in Stackdriver is embryronic, you can retrieve and visualize the collected metrics with a script, as described in the guide on [Reading Time Series](https://cloud.google.com/monitoring/custom-metrics/reading-metrics) and the -[custom metric code sample](https://github.com/GoogleCloudPlatform/python-docs-samples/blob/master/monitoring/api/v3/custom_metric.py). +[custom metric documentation](https://cloud.google.com/monitoring/custom-metrics). In addition to the included white-box monitoring, black-box monitoring should be set up to exercise the functionality of the registry platform as a user would diff --git a/docs/operational-procedures/reserved-list-management.md b/docs/operational-procedures/reserved-list-management.md index 7bc45a663af..577374c53a9 100644 --- a/docs/operational-procedures/reserved-list-management.md +++ b/docs/operational-procedures/reserved-list-management.md @@ -17,7 +17,7 @@ types are: allocation token at time of registration. This token is configured on an `AllocationToken` entity with a matching `domainName`, and is sent by the registrar using the - [allocation token EPP extension](https://tools.ietf.org/id/draft-ietf-regext-allocation-token-07.html). + [allocation token EPP extension](https://datatracker.ietf.org/doc/html/rfc8495). * **`RESERVED_FOR_ANCHOR_TENANT`** - Like `RESERVED_FOR_SPECIFIC_USE`, except for an anchor tenant (i.e. a registrant participating in a [Qualified Launch Program](https://newgtlds.icann.org/en/announcements-and-media/announcement-10apr14-en)),