From e225ee9e170346c9affec86ea3b9025c16a269a4 Mon Sep 17 00:00:00 2001 From: BohdanMar Date: Wed, 2 Sep 2026 17:28:08 +0200 Subject: [PATCH 1/2] docs: explain how to find the release ECP Add instructions for looking up the ReleasePlanAdmission name from the ReleasePlan labels, and mention the konflux-release-data repo as an alternative. Follow-up from review feedback on PR #246. --- .../ROOT/pages/early-policy-violations.adoc | 22 +++++++++++++++---- 1 file changed, 18 insertions(+), 4 deletions(-) diff --git a/modules/ROOT/pages/early-policy-violations.adoc b/modules/ROOT/pages/early-policy-violations.adoc index de9d6ce..b00bede 100644 --- a/modules/ROOT/pages/early-policy-violations.adoc +++ b/modules/ROOT/pages/early-policy-violations.adoc @@ -76,10 +76,24 @@ and another matching your release policy. === Step 1: Find your release policy configuration Your release policy is defined in the `ReleasePlanAdmission` in your managed -namespace. Ask your release engineering or SRE team for the -`EnterpriseContractPolicy` (ECP) name or configuration used in your release -pipeline. The value is typically in the format `namespace/name`, for example -`rhtap-releng-tenant/registry-rhtap-contract`. +namespace. To find it, look up your `ReleasePlan` and find the associated +`ReleasePlanAdmission` name: + +[,shell,subs="+quotes"] +---- +$ oc get releaseplan ____ -o yaml | yq .metadata.labels | grep release +---- + +The output includes a label like +`release.appstudio.openshift.io/releasePlanAdmission: `. Prepend the +managed namespace to get the full reference, for example +`rhtap-releng-tenant/`. + +You can also find this in the `konflux-release-data` repository by browsing +your tenant's `ReleasePlan` YAML files under +`tenants-config/auto-generated/cluster//tenants//`. + +Ask your release engineering or SRE team if you have trouble finding it. === Step 2: Create a non-blocking integration test From 055ec455d1cf7c87a07d7f13122f02ee7169a6a8 Mon Sep 17 00:00:00 2001 From: BohdanMar Date: Thu, 3 Sep 2026 15:28:36 +0200 Subject: [PATCH 2/2] =?UTF-8?q?docs:=20address=20review=20feedback=20?= =?UTF-8?q?=E2=80=94=20grep=20releasePlanAdmission,=20use=20rpa-name?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Use grep releasePlanAdmission for cleaner output, and use placeholder since we're finding the ReleasePlanAdmission name. --- modules/ROOT/pages/early-policy-violations.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/modules/ROOT/pages/early-policy-violations.adoc b/modules/ROOT/pages/early-policy-violations.adoc index b00bede..c1ffdaa 100644 --- a/modules/ROOT/pages/early-policy-violations.adoc +++ b/modules/ROOT/pages/early-policy-violations.adoc @@ -81,13 +81,13 @@ namespace. To find it, look up your `ReleasePlan` and find the associated [,shell,subs="+quotes"] ---- -$ oc get releaseplan ____ -o yaml | yq .metadata.labels | grep release +$ oc get releaseplan ____ -o yaml | yq .metadata.labels | grep releasePlanAdmission ---- The output includes a label like -`release.appstudio.openshift.io/releasePlanAdmission: `. Prepend the +`release.appstudio.openshift.io/releasePlanAdmission: `. Prepend the managed namespace to get the full reference, for example -`rhtap-releng-tenant/`. +`rhtap-releng-tenant/`. You can also find this in the `konflux-release-data` repository by browsing your tenant's `ReleasePlan` YAML files under