Skip to content
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

Issue-596: Holistic review of non-quarkus cloud chapter #625

Merged
merged 8 commits into from
May 23, 2024

Conversation

domhanak
Copy link
Contributor

Closes/Fixes/Resolves #596

Description:
Improvement to cloud sections

Please make sure that your PR meets the following requirements:

  • You have read the contributions doc
  • Pull Request title is properly formatted: Issue-XYZ Subject
  • Pull Request title contains the target branch if not targeting main: [0.9.x] Issue-XYZ Subject
  • The nav.adoc file has a link to this guide in the proper category
  • The index.adoc file has a card to this guide in the proper category, with a meaningful description
How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

@domhanak domhanak added the DO_NOT_MERGE 🙅 don't merge this PR label Apr 22, 2024
Copy link
Contributor

github-actions bot commented Apr 22, 2024

🎊 PR Preview 062ee8c has been successfully built and deployed. See the documentation preview: https://sonataflow-docs-preview-pr-625.surge.sh

Review build-and-deploy-workflows
Review configuring-workflows
Review developing-workflows
Review referencing-resource-files
Fix typoes in build and deploy workflows
Review building-custom-images
Review customize-podspec
Review workflow-status-conditions
@domhanak domhanak removed the DO_NOT_MERGE 🙅 don't merge this PR label May 22, 2024
@domhanak domhanak assigned wmedvede and jakubschwan and unassigned wmedvede and jakubschwan May 22, 2024
@@ -144,7 +122,7 @@ To uninstall the correct version of the operator, first you must get the current
----
kubectl get deployment sonataflow-operator-controller-manager -n sonataflow-operator-system -o jsonpath="{.spec.template.spec.containers[?(@.name=='manager')].image}"

quay.io/kiegroup/kogito-serverless-operator-nightly:1.41.0
quay.io/kiegroup/kogito-serverless-operator-nightly:latest
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ricardozanini noting these references, needs updates

@domhanak
Copy link
Contributor Author

Found some extra flaws, apologies. 👀 suggestions

Copy link
Contributor

@wmedvede wmedvede left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I have added minor suggestions.
Thanks!

@ricardozanini ricardozanini merged commit 245b4c7 into apache:main May 23, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Holistic review of non-quarkus cloud chapter
4 participants