Skip to content

Conversation

@amp-rh
Copy link
Contributor

@amp-rh amp-rh commented Dec 1, 2025

Updates all shared step files under ci-operator/step-registry/ibm-fusion-access/ to consistently use 'IBM Fusion Access' instead of 'Fusion Access' throughout documentation, comments, and echo messages.

Dependencies

Changes

  • shared-lib/: Update README, commands.sh, and ref.yaml with IBM branding
  • configure-aws-security-groups/: Update documentation
  • configure-kmm-registry/: Update comments and documentation
  • create-fusionaccess-resource/: Update documentation
  • create-namespaces/: Update echo messages
  • create-pull-secrets/: Update echo messages and documentation
  • install-fusion-access-operator/: Update echo messages and documentation

This rename standardizes the naming convention to use the full 'ibm-fusion-access'
prefix across all step registry components and CI configurations.

Changes:
- Rename interop-tests/fusion-access/ directory to interop-tests/ibm-fusion-access/
- Update all step names from interop-tests-fusion-access-* to interop-tests-ibm-fusion-access-*
- Update chain references in environment-setup-chain and ebs-integration-chain
- Rename CI config file to ibm-fusion-access-operator-ocp4.20-lp-interop
- Update CI config references to use renamed steps
- Regenerate metadata.json files and Prow jobs
Updates all shared step files under ci-operator/step-registry/ibm-fusion-access/
to consistently use 'IBM Fusion Access' instead of 'Fusion Access' throughout
documentation, comments, and echo messages.

Changes:
- shared-lib/: Update README, commands.sh, and ref.yaml with IBM branding
- configure-aws-security-groups/: Update documentation
- configure-kmm-registry/: Update comments and documentation
- create-fusionaccess-resource/: Update documentation
- create-namespaces/: Update echo messages
- create-pull-secrets/: Update echo messages and documentation
- install-fusion-access-operator/: Update echo messages and documentation
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 1, 2025

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 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 Dec 1, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 1, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: amp-rh
Once this PR has been reviewed and has the lgtm label, please assign rabin-io for approval. For more information see the Code Review Process.

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

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@amp-rh: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-RedHatQE-interop-testing-master-ibm-fusion-access-operator-ocp4.20-lp-interop-images RedHatQE/interop-testing presubmit Presubmit changed
periodic-ci-RedHatQE-interop-testing-master-ibm-fusion-access-operator-ocp4.20-lp-interop-ibm-fusion-access-operator-ipi-ocp420 N/A periodic Periodic changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

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

Labels

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.

2 participants