-
Notifications
You must be signed in to change notification settings - Fork 0
feat: onboard cloudpak 4 data #34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
successfully deployed using existing cluster - https://cloud.ibm.com/projects/08ef9093-8a07-4e29-a5e8-ad51d40b2f7d/configurations |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see latest
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm.. Just added one thing surrounding the README and pre-reqs that we should document
|
/run pipeline |
4 similar comments
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
TestRunStandardSolution 2025-06-12T14:47:25Z command.go:206: module.watsonx_self_managed_ocp.module.cloud_pak_deployer.helm_release.cloud_pak_deployer_helm_release: Still destroying... [id=cloud-pak-deployer, 10m0s elapsed]
TestRunStandardSolution 2025-06-12T14:47:26Z command.go:206: ╷
TestRunStandardSolution 2025-06-12T14:47:26Z command.go:206: │ Error: 1 error occurred:
TestRunStandardSolution 2025-06-12T14:47:26Z command.go:206: │ * timed out waiting for the conditiontimed out on destroy |
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
|
Going to merge this once pipeline green - @argeiger should it be a 2.0.0 release? |
Yes we can mark it as a 2.0.0 so we know that is the start of the catalog version |
|
🎉 This PR is included in version 2.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
3 similar comments
|
🎉 This PR is included in version 2.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Description
Release required?
x.x.X)x.X.x)X.x.x)Release notes content
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers