Skip to content

Conversation

@clcollins
Copy link
Member

@clcollins clcollins commented Feb 3, 2026

Summary

Improves validate-pull-secret-ext by aggregating multiple validation failures into a single service log instead of prompting for
each failure individually.

Changes

  • Aggregate failures: Collect all validation failures and send one service log at end
  • New flag: --skip-service-logs for testing/automation
  • New template: Uses pull_secret_multiple_sync_failures.json with FAILURE_LIST parameter
  • Better UX: Failures displayed in formatted list before service log prompt
  • Cleaner code: Removed obsolete helper functions, added comprehensive unit tests

Example Output

Pull Secret Validation Failures: Pull Secret Issues
Found 3 failure(s):

  1. cloud.openshift.com
  2. quay.io
  3. registry.redhat.io

[Service log prompt with all failures listed]

Dependencies

⚠️ Requires: openshift/managed-notifications#400 to be merged first (adds the new template)

Testing

  • ✅ All unit tests pass
  • ✅ No regressions
  • ⏳ Manual testing against live cluster (after template PR merges)

Related Issues

  • SREP-3365 - Main implementation card
  • SREP-3321 - Related validation improvements
  • SREP-3380 - Follow-up: Region Lead permissions evaluation

🤖 Generated with Claude Code

Aggregates multiple pull secret validation failures into a single service
log instead of prompting for each failure individually. This improves the
user experience and reduces service log noise.

Changes:
- Aggregate failures and send one service log at end of validation
- Add --skip-service-logs flag for testing/automation
- Use new pull_secret_multiple_sync_failures.json template
- Add helper functions: buildTemplateParameters, formatFailureDisplay,
  recordServiceLogFailure, sendAggregatedServiceLogs
- Update validation functions to record failures instead of sending immediately
- Remove obsolete sendPullSecretServiceLog and sendPullSecretMismatchServiceLog
- Add comprehensive unit tests for new functions

Related: SREP-3365, SREP-3321
Depends on: openshift/managed-notifications#400

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Signed-off-by: Chris Collins <collins.christopher@gmail.com>
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 3, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: clcollins

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 Feb 3, 2026
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. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant