Problem:
On release branches we don't use main images so the reviewdog for manifests is failing and we need to ignore it.
Solution:
If a branch is named release- then we will use the exact version and instead of perconalab use percona repository. The check will only be done for operator image and bundles, not for other images since we cannot know all the versions.
CHECKLIST
Jira
[ ] Is the Jira ticket created and referenced properly?
[ ] Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
[ ] Does the Jira ticket link to the proper milestone (Fix Version field)?
Tests
[ ] Is an E2E test/test case added for the new feature/change?
[ ] Are unit tests added where appropriate?
[ ] Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?
Config/Logging/Testability
[ ] Are all needed new/changed options added to default YAML files?
[ ] Did we add proper logging messages for operator actions?
[ ] Did we ensure compatibility with the previous version or cluster upgrade process?
[ ] Does the change support oldest and newest supported PXC version?
[ ] Does the change support oldest and newest supported Kubernetes version?
CHANGE DESCRIPTION
Problem: On release branches we don't use main images so the reviewdog for manifests is failing and we need to ignore it.
Solution: If a branch is named
release-then we will use the exact version and instead ofperconalabuseperconarepository. The check will only be done for operator image and bundles, not for other images since we cannot know all the versions.CHECKLIST
Jira
Needs Doc) and QA (Needs QA)?Tests
compare/*-oc.yml)?Config/Logging/Testability