From 7746b8b732ee6ee1cfc3323860f9469a5a9663ab Mon Sep 17 00:00:00 2001 From: BigEars Date: Wed, 14 Jan 2026 14:43:40 -0500 Subject: [PATCH] Update URL for argocd manifest --- .../rhdh-plugins-reference/argocd/argocd-plugin-admin.adoc | 2 +- modules/dynamic-plugins/proc-enabling-argo-cd-rollouts.adoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/artifacts/rhdh-plugins-reference/argocd/argocd-plugin-admin.adoc b/artifacts/rhdh-plugins-reference/argocd/argocd-plugin-admin.adoc index 94cac31f41..33676b1fd0 100644 --- a/artifacts/rhdh-plugins-reference/argocd/argocd-plugin-admin.adoc +++ b/artifacts/rhdh-plugins-reference/argocd/argocd-plugin-admin.adoc @@ -115,7 +115,7 @@ kubernetes: * If the Backstage Kubernetes plugin is already configured, the `ClusterRole` permissions for Rollouts and AnalysisRuns might already be granted. -* Use the link:https://raw.githubusercontent.com/backstage/community-plugins/main/workspaces/redhat-argocd/plugins/argocd/manifests/clusterrole.yaml[prepared manifest] to provide read-only `ClusterRole` access to both the Kubernetes and ArgoCD plugins. +* Use the link:https://raw.githubusercontent.com/backstage/community-plugins/main/workspaces/argocd/plugins/argocd/manifests/clusterrole.yaml[prepared manifest] to provide read-only `ClusterRole` access to both the Kubernetes and ArgoCD plugins. ==== .. If the `ClusterRole` permission is not granted, use the following YAML manifest to create the `ClusterRole`: diff --git a/modules/dynamic-plugins/proc-enabling-argo-cd-rollouts.adoc b/modules/dynamic-plugins/proc-enabling-argo-cd-rollouts.adoc index 511d4afb99..febfb7d829 100644 --- a/modules/dynamic-plugins/proc-enabling-argo-cd-rollouts.adoc +++ b/modules/dynamic-plugins/proc-enabling-argo-cd-rollouts.adoc @@ -41,7 +41,7 @@ kubernetes: * If the Backstage Kubernetes plugin is already configured, the `ClusterRole` permissions for Rollouts and AnalysisRuns might already be granted. -* Use the link:https://raw.githubusercontent.com/backstage/community-plugins/main/workspaces/redhat-argocd/plugins/argocd/manifests/clusterrole.yaml[prepared manifest] to provide read-only `ClusterRole` access to both the Kubernetes and ArgoCD plugins. +* Use the link:https://raw.githubusercontent.com/backstage/community-plugins/main/workspaces/argocd/plugins/argocd/manifests/clusterrole.yaml[prepared manifest] to provide read-only `ClusterRole` access to both the Kubernetes and ArgoCD plugins. ==== .. If the `ClusterRole` permission is not granted, use the following YAML manifest to create the `ClusterRole`: