From b2cbd7a3c69130e6c193e5e02ba7d2e3a40cf45b Mon Sep 17 00:00:00 2001 From: Samuele Perticarari Date: Wed, 4 Feb 2026 14:35:37 +0100 Subject: [PATCH] fix: Fixed external broken links (#3703) --- adrs/fast/README.md | 2 +- adrs/modules/README.md | 2 +- fast/project-templates/devops-azure-wif/README.md | 2 +- fast/project-templates/managed-kafka/README.md | 2 +- fast/stages/3-gke-dev/README.md | 4 ++-- modules/folder/README.md | 2 +- .../recipe-cross-reg-int-app-lb-vm-dns/README.md | 2 +- modules/organization/README.md | 2 +- modules/project/README.md | 2 +- modules/projects-data-source/README.md | 2 +- 10 files changed, 11 insertions(+), 11 deletions(-) diff --git a/adrs/fast/README.md b/adrs/fast/README.md index d6c722c23..1d687e9ab 100644 --- a/adrs/fast/README.md +++ b/adrs/fast/README.md @@ -1,3 +1,3 @@ # FAST architectural documents -This folder contains assorted bits of documentation used to log current architectural choices, or past decisions. Format is inspired by [Michael Nygard's decision record template](https://github.com/joelparkerhenderson/architecture-decision-record/blob/main/templates/decision-record-template-by-michael-nygard/index.md). +This folder contains assorted bits of documentation used to log current architectural choices, or past decisions. Format is inspired by [Michael Nygard's decision record template](https://github.com/joelparkerhenderson/architecture-decision-record/blob/main/locales/en/templates/decision-record-template-by-michael-nygard/index.md). diff --git a/adrs/modules/README.md b/adrs/modules/README.md index da5c91819..dcbb07457 100644 --- a/adrs/modules/README.md +++ b/adrs/modules/README.md @@ -1,3 +1,3 @@ # Fabric modules architectural documents -This folder contains assorted bits of documentation used to log current architectural choices, or past decisions. Format is inspired by [Michael Nygard's decision record template](https://github.com/joelparkerhenderson/architecture-decision-record/blob/main/templates/decision-record-template-by-michael-nygard/index.md). +This folder contains assorted bits of documentation used to log current architectural choices, or past decisions. Format is inspired by [Michael Nygard's decision record template](https://github.com/joelparkerhenderson/architecture-decision-record/blob/main/locales/en/templates/decision-record-template-by-michael-nygard/index.md). diff --git a/fast/project-templates/devops-azure-wif/README.md b/fast/project-templates/devops-azure-wif/README.md index eaecb49f9..f5ab45ec3 100644 --- a/fast/project-templates/devops-azure-wif/README.md +++ b/fast/project-templates/devops-azure-wif/README.md @@ -209,7 +209,7 @@ Three sample pipelines are provided as examples: - `pr-pipeline.yaml`: a "PR pipeline" that runs Terraform init, validate, and plan on pull requests. It posts the plan output as a comment to the PR and updates the PR status. - `merge-pipeline.yaml`: a "merge pipeline" that runs Terraform init, validate, and apply on merges to the main branch. -Each of the above pipelines needs to be edited to match your project id and resource names. Once that has been done, the code can be copy/pasted on a new pipeline in Azure Devops. On first run, you might be asked to grant permissions to the pipeline on the service connection. Refer to the Azure Devops [Pipelines Schema Reference](https://learn.microsoft.com/en-us/azure/devops/pipelines/yaml-schema/view=azure-pipelines) can be used for further customizations. +Each of the above pipelines needs to be edited to match your project id and resource names. Once that has been done, the code can be copy/pasted on a new pipeline in Azure Devops. On first run, you might be asked to grant permissions to the pipeline on the service connection. Refer to the Azure Devops [Pipelines Schema Reference](https://learn.microsoft.com/en-us/azure/devops/pipelines/yaml-schema/?view=azure-pipelines) can be used for further customizations. ### Branch Policies and Permissions diff --git a/fast/project-templates/managed-kafka/README.md b/fast/project-templates/managed-kafka/README.md index dec061fbc..57588511b 100644 --- a/fast/project-templates/managed-kafka/README.md +++ b/fast/project-templates/managed-kafka/README.md @@ -1,6 +1,6 @@ # Managed Kafka Cluster with Topics -This setup allows creating and configuring a managed Kafka cluster using [Google Cloud Managed Service for Apache Kafka](https://cloud.google.com/managed-service-for-apache-kafka), with configurable topics, networking, and labels. It is designed to be FAST-compliant and integrates seamlessly with existing Google Cloud infrastructure. +This setup allows creating and configuring a managed Kafka cluster using [Google Cloud Managed Service for Apache Kafka](https://cloud.google.com/products/managed-service-for-apache-kafka), with configurable topics, networking, and labels. It is designed to be FAST-compliant and integrates seamlessly with existing Google Cloud infrastructure. ## Prerequisites diff --git a/fast/stages/3-gke-dev/README.md b/fast/stages/3-gke-dev/README.md index cf8a63421..1a523822b 100644 --- a/fast/stages/3-gke-dev/README.md +++ b/fast/stages/3-gke-dev/README.md @@ -30,7 +30,7 @@ Some high level choices applied here: - Logging and monitoring uses Cloud Operations for system components and user workloads. - [GKE metering](https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-usage-metering) is enabled by default and stored in a BigQuery dataset created within the project. - [GKE Fleet](https://cloud.google.com/kubernetes-engine/docs/fleets-overview) can be optionally with support for the following features: - - [Fleet workload identity](https://cloud.google.com/anthos/fleet-management/docs/use-workload-identity) + - [Fleet workload identity](https://docs.cloud.google.com/kubernetes-engine/fleet-management/docs/use-workload-identity) - [Config Management](https://cloud.google.com/anthos-config-management/docs/overview) - [Service Mesh](https://cloud.google.com/service-mesh/docs/overview) - [Identity Service](https://cloud.google.com/anthos/identity/setup/fleet) @@ -158,7 +158,7 @@ If clusters share similar configurations, those can be centralized via `locals` Fleet management is entirely optional, and uses two separate variables: -- `fleet_config`: specifies the [GKE fleet](https://cloud.google.com/anthos/fleet-management/docs/fleet-concepts#fleet-enabled-components) features to activate +- `fleet_config`: specifies the [GKE fleet](https://docs.cloud.google.com/kubernetes-engine/fleet-management/docs/fleet-concepts#fleet-enabled-components) features to activate - `fleet_configmanagement_templates`: defines configuration templates for specific sets of features ([Config Management](https://cloud.google.com/anthos-config-management/docs/how-to/install-anthos-config-management) currently) Clusters can then be configured for fleet registration and one of the config management templates attached via the cluster-level `fleet_config` attribute. diff --git a/modules/folder/README.md b/modules/folder/README.md index c917a982d..56e1a555a 100644 --- a/modules/folder/README.md +++ b/modules/folder/README.md @@ -130,7 +130,7 @@ module "folder" { ## Privileged Access Manager (PAM) Entitlements -[Privileged Access Manager](https://cloud.google.com/iam/docs/privileged-access-manager-overview) entitlements can be defined via the `pam_entitlements` variable. +[Privileged Access Manager](https://docs.cloud.google.com/iam/docs/pam-overview) entitlements can be defined via the `pam_entitlements` variable. Note that using PAM entitlements requires specific roles to be granted to the users and groups that will be using them. For more information, see the [official documentation](https://cloud.google.com/iam/docs/pam-permissions-and-setup#before-you-begin). diff --git a/modules/net-lb-app-int-cross-region/recipe-cross-reg-int-app-lb-vm-dns/README.md b/modules/net-lb-app-int-cross-region/recipe-cross-reg-int-app-lb-vm-dns/README.md index 1bdd5a9a6..e6cbb3489 100644 --- a/modules/net-lb-app-int-cross-region/recipe-cross-reg-int-app-lb-vm-dns/README.md +++ b/modules/net-lb-app-int-cross-region/recipe-cross-reg-int-app-lb-vm-dns/README.md @@ -3,7 +3,7 @@ This recipe shows an actual usage scenario for the [cross-region internal application load balancer](../README.md) by implementing the [example provided in the GCP documentation](https://cloud.google.com/load-balancing/docs/l7-internal/setting-up-l7-cross-reg-internal).

- Scenario diagram. + Scenario diagram.

diff --git a/modules/organization/README.md b/modules/organization/README.md index 7ad46d206..1b8fd2126 100644 --- a/modules/organization/README.md +++ b/modules/organization/README.md @@ -263,7 +263,7 @@ custom.dataprocNoMoreThan10Workers: ## Privileged Access Manager (PAM) Entitlements -[Privileged Access Manager](https://cloud.google.com/iam/docs/privileged-access-manager-overview) entitlements can be defined via the `pam_entitlements` variable. +[Privileged Access Manager](https://docs.cloud.google.com/iam/docs/pam-overview) entitlements can be defined via the `pam_entitlements` variable. Note that using PAM entitlements requires specific roles to be granted to the users and groups that will be using them. For more information, see the [official documentation](https://cloud.google.com/iam/docs/pam-permissions-and-setup#before-you-begin). diff --git a/modules/project/README.md b/modules/project/README.md index 33e9b91a9..a28ac5213 100644 --- a/modules/project/README.md +++ b/modules/project/README.md @@ -1530,7 +1530,7 @@ cpus-ew8: ## Privileged Access Manager (PAM) Entitlements -[Privileged Access Manager](https://cloud.google.com/iam/docs/privileged-access-manager-overview) entitlements can be defined via the `pam_entitlements` variable. +[Privileged Access Manager](https://docs.cloud.google.com/iam/docs/pam-overview) entitlements can be defined via the `pam_entitlements` variable. Note that using PAM entitlements requires specific roles to be granted to the users and groups that will be using them. For more information, see the [official documentation](https://cloud.google.com/iam/docs/pam-permissions-and-setup#before-you-begin). diff --git a/modules/projects-data-source/README.md b/modules/projects-data-source/README.md index c5a19d76c..d5cc30474 100644 --- a/modules/projects-data-source/README.md +++ b/modules/projects-data-source/README.md @@ -1,6 +1,6 @@ # Projects Data Source Module -This module extends functionality of [google_projects](https://registry.terraform.io/providers/hashicorp/google/latest/docs/data-sources/projects) data source by retrieving all the projects under a specific `parent` recursively with only one API call against [Cloud Asset Inventory](https://cloud.google.com/asset-inventory) service. +This module extends functionality of [google_projects](https://registry.terraform.io/providers/hashicorp/google/latest/docs/data-sources/projects) data source by retrieving all the projects under a specific `parent` recursively with only one API call against [Cloud Asset Inventory](https://cloud.google.com/asset-inventory/docs) service. A good usage pattern would be when we want all the projects under a specific folder (including nested subfolders) to be included into [VPC Service Controls](../vpc-sc/). Instead of manually maintaining the list of project numbers as an input to the `vpc-sc` module we can use that module to retrieve all the project numbers dynamically.