-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[SRVLOGIC-469]: Deploying workflows chapter does not use kn worklow plugin #85916
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
base: serverless-docs-main
Are you sure you want to change the base?
Conversation
Now it uses the kn workflow plugin
50a1b1d
to
0537eaa
Compare
Hi @domhanak. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
modules/serverless-logic-building-deploying-workflow-preview-mode.adoc
Outdated
Show resolved
Hide resolved
modules/serverless-logic-building-deploying-workflow-preview-mode.adoc
Outdated
Show resolved
Hide resolved
Need to also fix the devmode and the other referenced guide. Ty for review, so far will ping you when I push the changes |
/ok-to-test |
🤖 Thu Jan 16 15:24:14 - Prow CI generated the docs preview: |
modules/serverless-logic-building-deploying-workflow-preview-mode.adoc
Outdated
Show resolved
Hide resolved
modules/serverless-logic-building-deploying-workflow-preview-mode.adoc
Outdated
Show resolved
Hide resolved
modules/serverless-logic-building-deploying-workflow-preview-mode.adoc
Outdated
Show resolved
Hide resolved
modules/serverless-logic-building-deploying-workflow-preview-mode.adoc
Outdated
Show resolved
Hide resolved
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.
A minor suggestions. Otherwise, LGTM!
@domhanak Once you have drafted the content, you can assign this PR for the peer review process by adding a Note: Make sure you have squashed down the commit to only 1. The OpenShift peer review squad will then peer review this PR, and you can proceed with the merge review process. |
Review from Kalyani Co-authored-by: Kalyani Desai <[email protected]>
Reorder docs to make more sense and follow the precedures from basic (what user should do 1st, to more complex ones )
Removes the example workflow from the module and replaces it with prerequsites that user should have the WF deployed. Adds steps to query all services.
@domhanak You want me to put this on the peer review as well? |
Unify namespace usage. Use shorthand -n where possible. Add Testing section to deploying-workflows-dev-mode
@kaldesai not yet I still feel like some parts can be enhanced. I ll ping you :) |
@domhanak: all tests passed! 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-sigs/prow repository. I understand the commands that are listed here. |
@domhanak Do you want me to put this on the peer review as well? |
@kaldesai if you think it is ok please do |
/label peer-review-needed |
---- | ||
+ | ||
.Example command for the `greetings-workflow.yaml` file: | ||
.Example command for a workflow that has ID attribute with value `greeting`: |
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.
No colons for titles:
.Example command for a workflow that has ID attribute with value `greeting`: | |
.Example command for a workflow that has an ID attribute with value `greeting` |
$ oc logs pod/<pod-name> -n <namespace> | ||
---- | ||
|
||
.Cleanup |
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.
Technically .Cleanup
is a non-standard heading for a procedure module (per modular docs guide). FWIW, I see only 1 other instance in the repo (though, that one has it as .Clean up
two-words; the single-word here is correctly what IBM Style Guide suggests).
Could this instead just be the last step in the normal .Procedure
? Or maybe the last step in .Verification
? Alternatively, could be split out into its own procedure module "Cleaning up a workflow deployment" but that seems like overkill.
---- | ||
|
||
.Cleanup | ||
. To cleanup the deployment, delete the projects resources running the following command: |
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.
Either way though, if this stays as a single-step procedure, use an unordered list (per guidelines) and use "by running":
. To cleanup the deployment, delete the projects resources running the following command: | |
* To cleanup the deployment, delete the projects resources by running the following command: |
. To deploy the application, apply the YAML file by entering the following command: | ||
. In your terminal, navigate to the root directory of your {ServerlessLogicProductName} project. | ||
|
||
. Deploy the application, by running the following command: |
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.
. Deploy the application, by running the following command: | |
. Deploy the application by running the following command: |
---- | ||
|
||
.Testing |
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.
Same thought re: non-standard heading for this .Testing
one. This one, however, feels like splitting it out as its own procedure would be worthwhile (versus including it within some other procedure module).
Edit: I see now there already is a "Testing a deployment" procedure later in the assembly. Is that basically the same procedure that's being shown here? If so, could there just be an "Additional resources" link to that procedure from this one instead of duplicating?
+ | ||
Note the value of `HOST/PORT` from the result of tis command, referenced as `<WORKFLOW_URL>` in next step. | ||
|
||
.. Navigate to the `<WORKFLOW_URL>/q/dev-ui/org.apache.kie.sonataflow.sonataflow-quarkus-devui/workflows` in your browser. Please note that it may take some time until the management console is available. |
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.
Re: previous comment, match lowercase here as well, if you change the other:
.. Navigate to the `<WORKFLOW_URL>/q/dev-ui/org.apache.kie.sonataflow.sonataflow-quarkus-devui/workflows` in your browser. Please note that it may take some time until the management console is available. | |
.. Navigate to the `<workflow_url>/q/dev-ui/org.apache.kie.sonataflow.sonataflow-quarkus-devui/workflows` in your browser. Please note that it may take some time until the management console is available. |
+ | ||
Note the value of `HOST/PORT` from the result of tis command, referenced as `<WORKFLOW_URL>` in next step. | ||
|
||
.. Navigate to the `<WORKFLOW_URL>/q/dev-ui/org.apache.kie.sonataflow.sonataflow-quarkus-devui/workflows` in your browser. Please note that it may take some time until the management console is available. |
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.
- Don't need "please", or maybe even "note".
- "might" instead of "may" (better for translation).
.. Navigate to the `<WORKFLOW_URL>/q/dev-ui/org.apache.kie.sonataflow.sonataflow-quarkus-devui/workflows` in your browser. Please note that it may take some time until the management console is available. | |
.. Navigate to the `<WORKFLOW_URL>/q/dev-ui/org.apache.kie.sonataflow.sonataflow-quarkus-devui/workflows` in your browser. It might take some time until the management console is available. |
|
||
.. Navigate to the `<WORKFLOW_URL>/q/dev-ui/org.apache.kie.sonataflow.sonataflow-quarkus-devui/workflows` in your browser. Please note that it may take some time until the management console is available. | ||
|
||
|
||
.Next steps |
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.
This single-step .Next steps
procedure could probably just be absorbed into wherever the .Testing
procedure above it ends up.
@@ -13,62 +13,22 @@ You can verify that your {ServerlessLogicProductName} workflow is running by per | |||
* You have an {ServerlessLogicOperatorName} installed on your cluster. | |||
* You have access to an {ServerlessLogicProductName} project with the appropriate roles and permissions to create applications and other workloads in {ocp-product-title}. | |||
* You have installed the OpenShift CLI `(oc)`. | |||
* You have deployed your workflow in preview mode in the {ocp-product-title}. |
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.
Drop "the":
* You have deployed your workflow in preview mode in the {ocp-product-title}. | |
* You have deployed your workflow in preview mode in {ocp-product-title}. |
|
||
.Procedure | ||
|
||
. Create a workflow `YAML` file similar to the following: | ||
. Retrieve the list of service and identify the one matching `name` of your workflow: |
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.
Should this be plural?
. Retrieve the list of service and identify the one matching `name` of your workflow: | |
. Retrieve the list of services and identify the one matching the `name` of your workflow: |
@adellape You made me think hard about the guide and how it looks as whole. I am trying to improve it |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Now it uses the kn workflow plugin
Version(s):
serverless-docs-1.34
serverless-docs-1.35
Issue:
SRVLOGIC-269
Link to docs preview:
Preview
QE review:
Additional information:
@kaldesai @wmedvede @ricardozanini PTAL