multicluster-global-hub
multicluster-global-hub copied to clipboard
stolostron
:sparkles :bug: Add Relationship and correct the update operations
Summary
- distinguish create and update inspired from https://github.com/stolostron/multicluster-global-hub/pull/1154 Thanks @yanmxa
- Correct the usage for update and delete
- Add labels to the request metadata
- Add relationship for the policy to show the status
Related issue(s)
Fixes #https://issues.redhat.com/browse/ACM-14812
Tests
- [ ] Unit/function tests have been added and incorporated into
make unit-tests. - [ ] Integration tests have been added and incorporated into
make integration-test. - [ ] E2E tests have been added and incorporated into
make e2e-test-all. - [ ] List other manual tests you have done.
Quality Gate passed
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
74.5% Coverage on New Code
0.0% Duplication on New Code
See analysis details on SonarCloud
![sonarqubecloud[bot] avatar](https://avatars.githubusercontent.com/in/12526?v=4 "Published by a pub.dev verified publisher"){kind=small}
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: clyang82, yanmxa
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [clyang82,yanmxa]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@clyang82: new pull request created: #1164
In response to this:
/cherry-pick release-2.12
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.
@clyang82: new pull request created: #1217
In response to this:
/cherry-pick release-2.12
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.