Skip to content

docs: explain how to find the release ECP #249

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
BohdanMar wants to merge 4 commits into
base: main
Choose a base branch
from
+24 −5
Open

docs: explain how to find the release ECP #249

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
e225ee9
docs: explain how to find the release ECP
BohdanMar Sep 2, 2026
055ec45
docs: address review feedback — grep releasePlanAdmission, use rpa-name
BohdanMar Sep 3, 2026
3f670fe
docs: fix Step 1 to extract ECP from RPA
BohdanMar Sep 7, 2026
ecd920d
docs: add namespace flags and use yq for copy-pasteable output
BohdanMar Sep 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 24 additions & 5 deletions modules/ROOT/pages/early-policy-violations.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,11 +75,30 @@ 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`.
Your release policy is defined in the `ReleasePlanAdmission` (RPA) in your
managed namespace. First, find the RPA name from your `ReleasePlan` (run this
in your tenant namespace):

[,shell,subs="+quotes"]
Comment thread
BohdanMar marked this conversation as resolved.
----
$ oc get releaseplan __<releaseplan-name>__ -n __<tenant-namespace>__ -o yaml | yq -r '.metadata.labels["release.appstudio.openshift.io/releasePlanAdmission"]'
----

Then extract the `EnterpriseContractPolicy` (ECP) reference from the RPA:

[,shell,subs="+quotes"]
----
$ oc get releaseplanadmission __<rpa-name>__ -n __<managed-namespace>__ -o yaml | yq -r .spec.policy
----

The output is the ECP reference to use in `POLICY_CONFIGURATION`, typically in
the format `namespace/name` (for example `rhtap-releng-tenant/registry-rhtap-contract`).

You can also find this in the `konflux-release-data` repository by browsing
your tenant's `ReleasePlanAdmission` YAML files under
`tenants-config/auto-generated/cluster/<cluster>/tenants/<tenant>/`.

Ask your release engineering or SRE team if you have trouble finding it.

=== Step 2: Create a non-blocking integration test

Expand Down
Loading