Update ibm-fusion-access shared steps to use consistent IBM branding#72019
Conversation
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
|
Skipping CI for Draft Pull Request. |
|
@kmk142789: changing LGTM is restricted to collaborators DetailsIn response to this: 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. |
|
[REHEARSALNOTIFIER] Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
@amp-rh: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
@kmk142789420-stack: changing LGTM is restricted to collaborators DetailsIn response to this: 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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: amp-rh, dfrazzette, kmk142789420-stack The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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 brandingconfigure-aws-security-groups/: Update documentationconfigure-kmm-registry/: Update comments and documentationcreate-fusionaccess-resource/: Update documentationcreate-namespaces/: Update echo messagescreate-pull-secrets/: Update echo messages and documentationinstall-fusion-access-operator/: Update echo messages and documentation