Repository navigation
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Summary
Merge Risk: ⚪ Minimal · up to
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Signed-off-by: Jonathan West <jgwest@gmail.com>
d57effa to
abd415a
Compare
What does this PR do?
Courtesy of claude:
1-002-validate_backend_service_test.go + 1-026-validate_backend_service_permissions_test.go — both had an identical It("validates backend service permissions", ...) checking the same cluster Deployment/Service in openshift-gitops. Merged into 1-002, folding in 026's ServiceAccount/ClusterRole/ClusterRoleBinding assertions. Deleted 1-026.
1-105_validate_default_argocd_route_test.go + 1-111_validate_default_argocd_route_test.go — functionally identical: both verify the default openshift-gitops-server Route/TLS secret and both mutate .spec.server.route.tls to Passthrough/None and re-verify. Kept 1-105 (uses the richer routeFixture matchers), deleted 1-111.
1-074_validate_terminating_namespace_block_test.go + 1-102_validate_handle_terminating_namespaces_test.go — same scenario (a managed namespace stuck terminating due to a finalizer must not block reconciliation of other managed namespaces). 1-102 is a strict superset — it does everything 1-074 does (verify RoleBindings appear in the second namespace) plus an actual Application deploy/sync check. Deleted 1-074, kept 1-102.
I've humanly verified that we're not losing test coverage with the result.
PR acceptance criteria:
make serve-docsWhat type of PR is this?
/kind cleanup
Special notes to the reviewer: