Skip to content

[release-4.20] MGMT-21854: fix registries.conf generation for multiple yaml mirror files#544

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.20from
andfasano:cherrypick-296a219-to-release-4.20
Sep 29, 2025
Merged

[release-4.20] MGMT-21854: fix registries.conf generation for multiple yaml mirror files#544
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.20from
andfasano:cherrypick-296a219-to-release-4.20

Conversation

@andfasano
Copy link
Contributor

This is a manual cherry-pick of #543

/assign @danielerez

…iles (openshift#543)

* fix registries.conf generation for multiple yaml mirror files

* use GetMultipleYamls for manifests parsing
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 29, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 29, 2025

@andfasano: This pull request references MGMT-21854 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.20.0" version, but no target version was set.

Details

In response to this:

This is a manual cherry-pick of #543

/assign @danielerez

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 openshift-eng/jira-lifecycle-plugin repository.

@danielerez
Copy link
Contributor

/approve

@danielerez
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 29, 2025
@openshift-ci
Copy link

openshift-ci bot commented Sep 29, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andfasano, danielerez

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 29, 2025
@openshift-ci
Copy link

openshift-ci bot commented Sep 29, 2025

@andfasano: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 10d51a6 into openshift:release-4.20 Sep 29, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants