multicluster-observability-operator
multicluster-observability-operator copied to clipboard
Use semantic.DeepEqual for Kubernetes Obj comparison
https://issues.redhat.com/browse/ACM-13688
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: coleenquadros
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [coleenquadros]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Quality Gate passed
Issues
1 New issue
0 Accepted issues
Measures
0 Security Hotspots
76.0% Coverage on New Code
0.0% Duplication on New Code
@coleenquadros: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/test-unit | 0b7d2f28d2a99a1cb29a6e8d06f7d42759e10951 | link | true | /test test-unit |
| ci/prow/test-e2e | 0b7d2f28d2a99a1cb29a6e8d06f7d42759e10951 | link | true | /test test-e2e |
Full PR test history. Your PR dashboard.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.
This is a risky change to validate so close to the new release. I've had issues in the past where using deepEqual could trigger infinite reconciliations because some default fields were set on the runtime object while the desired object would not have them.
PR needs rebase.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.