Closed lmzuccarelli closed 1 month ago
@lmzuccarelli: This pull request references Jira Issue OCPBUGS-42428, which is invalid:
Comment /jira refresh
to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
The bug has been updated to refer to the pull request using the external bug tracker.
/jira refresh
@lmzuccarelli: This pull request references Jira Issue OCPBUGS-42428, which is valid. The bug has been moved to the POST state.
Requesting review from QA contact: /cc @zhouying7780
Currently all the cluster resources being generated by oc-mirror v2 are in yaml.
Is there any reason why we are generating the signature config map both in yaml and json ?
Is it possible to have the fields of the yaml file ordered like the other cluster resources (CatalogSource, IDMS, ITMS and UpdateService) ?
apiVersion:
kind:
metadata:
binaryData:
For the cluster the order does not make any different, but for the cluster admin when doing a manual check in the file, it could be useful.
Other then my previous comments, it LGTM.
I ran the steps mentioned in the description, everything worked as expected.
Thanks @lmzuccarelli
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: aguidirh, lmzuccarelli
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@lmzuccarelli: all tests passed!
Full PR test history. Your PR dashboard.
@lmzuccarelli: Jira Issue OCPBUGS-42428: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-42428 has been moved to the MODIFIED state.
[ART PR BUILD NOTIFIER]
Distgit: oc-mirror-plugin This PR has been included in build oc-mirror-plugin-container-v4.18.0-202410091810.p0.g9665b42.assembly.stream.el9. All builds following this will include this PR.
Description
This fix ensures that the siagnature configmap yaml and json files created in clusterresource does not have duplicates
Fixes # OCPBUGS-42428
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Locally
Use the following imagesetconfig
Execute mirror-to-disk
Then execute disk-to-mirror
There should be no duplicate entries in the yaml or json config maps created in working-dir/cluster-resources
Expected Outcome
yaml configmap output (in this case only 3 entries ) with no duplicates
i.e sha256-xxxx-id where "xxxx" is not duplicated