Skip to content

Conversation

adamviktora
Copy link
Member

@adamviktora adamviktora commented Sep 5, 2025

  • adds support for multiple yaml path in a filter key
    • key should be formatted as some.spec|some.other.spec
    • needed for filter by Operating system to work on the proxy side
  • refactoring of a nested for loop

- key should be formatted as some.spec|some.other.spec
- needed for filter by Operating system
- refactoring of a nested for loop
@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Sep 5, 2025

@adamviktora: This pull request references CNV-67729 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.21.0" version, but no target version was set.

In response to this:

  • adds support for multiple yaml paths as filter keys
  • key should be formatted as some.spec|some.other.spec
  • needed for filter by Operating system to work on the proxy side
  • refactoring of a nested for loop

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.

Copy link

openshift-ci bot commented Sep 5, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: adamviktora

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

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

@adamviktora adamviktora changed the title CNV-67729: support multiple yaml paths as filter keys CNV-67729: support multiple yaml paths in a filter key Sep 5, 2025
@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Sep 5, 2025

@adamviktora: This pull request references CNV-67729 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.21.0" version, but no target version was set.

In response to this:

  • adds support for multiple yaml path in a filter key
  • key should be formatted as some.spec|some.other.spec
  • needed for filter by Operating system to work on the proxy side
  • refactoring of a nested for loop

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants