feat: Prepare community operators scripts to add new bundles format

[flacatus]

Signed-off-by: Flavius Lacatusu flacatus@redhat.com

What does this PR do?

This PR prepare the community operators to have new bundles format

Screenshot/screencast of this PR

What issues does this PR fix or reference?

eclipse-che/che#19244

How to test this PR?

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix
• Custom resource definition file is up to date
• OLM bundles are up to date
• The repository devfile is up to date and works
• Sections What issues does this PR fix or reference and How to test this PR completed
• Relevant user documentation updated
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

[flacatus]

We can merge after 7.35.2

[mmorhun]

LGTM

[AndrienkoAleksandr]

Hello, @flacatus, @tolusha. I see in the community update script we are using migration from new bundle to old format bundle command:

che-operator/olm/prepare-community-operators-update.sh

Line 68 in 86d748b

${OPM_BINARY} index export --index="${INDEX_IMAGE}" --package="${packageName}" -c="docker" --download-folder "${manifestPackagesDir}"

Then we recopy files from old format to follow new bundle format file locations. Maybe in the frame of the issue: we should remove it eclipse-che/che#19244 and copy bundle from https://github.com/eclipse-che/che-operator/tree/86d748bee0de01756fd503bf418b677f4f6283be/bundle folder ? Or Did I misunderstand something?

[flacatus]

https://github.com/eclipse-che/che-operator/tree/86d748bee0de01756fd503bf418b677f4f6283be/bundle

Make sense to copy from https://github.com/eclipse-che/che-operator/tree/86d748bee0de01756fd503bf418b677f4f6283be/bundle

[flacatus]

Maybe we can move the function:

source ${OPERATOR_REPO}/.github/bin/common.sh
getLatestsStableVersions

to olm/prepare-community-operators-update.sh

[openshift-ci]

@flacatus: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Rerun command
ci/prow/v7-devworkspace-happy-path	5a8c858	link	/test v7-devworkspace-happy-path
ci/prow/v7-multi-host-next-deployment	5a8c858	link	/test v7-multi-host-next-deployment

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

[AndrienkoAleksandr]

Suggested change

	LAST_PACKAGE_VERSION="$LAST_PACKAGE_VERSION-all-namespaces"
	LAST_PACKAGE_VERSION="${LAST_PACKAGE_VERSION}-all-namespaces"

[AndrienkoAleksandr]

I think variable https://github.com/eclipse-che/che-operator/pull/1041/files#diff-87596dbd1244260e3d5bf59cc959c0aa3739edc345d88892fc7c6d8f3eaef2c8R115 is not used any more, so you can remove it.

[AndrienkoAleksandr]

Great job!

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AndrienkoAleksandr, flacatus, mmorhun

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

Needs approval from an approver in each of these files:

• OWNERS

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