-
Notifications
You must be signed in to change notification settings - Fork 1.8k
RHDEVDOCS-4476: key features in odo 3.0 #51192
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
🤖 Updated build preview is available at: Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/1749 |
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.
Looks great, left some minor suggestions, PTAL.
modules/odo-new-commands-30.adoc
Outdated
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.
nit: the --details
flag.
e82d6b1
to
cdd7ee9
Compare
/lgtm |
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.
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.
You are already using 'v2' and 'v3' in the migration doc, it would be nice if you can use the same in this doc instead of 'version 2' and 'version 3'.
|
||
== odo dev | ||
|
||
The `odo dev` command allows you to code, build, run, debug, and test your applications on the cluster in a continuous workflow. It combines the `odo push` and `odo watch` commands from `odo` version 2 into a single 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.
The `odo dev` command allows you to code, build, run, debug, and test your applications on the cluster in a continuous workflow. It combines the `odo push` and `odo watch` commands from `odo` version 2 into a single command. | |
The `odo dev` command allows you to code, build, run, debug, and test your applications on the cluster in a continuous workflow. It combines the `odo push` and `odo watch` commands from `odo` v2 into a single command. |
Work without a running application:: Compared to version 2, the `odo add binding` command does not require the application to be running on the cluster, making it even faster. | ||
|
||
Only supports bindable Operators:: | ||
The version 2 `odo link` command links an application to another application and any Operator-backed service. However, `odo` version 3 currently only supports connecting to services backed by Operators that are considered bindable by the Service Binding Operator. |
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.
Work without a running application:: Compared to version 2, the `odo add binding` command does not require the application to be running on the cluster, making it even faster. | |
Only supports bindable Operators:: | |
The version 2 `odo link` command links an application to another application and any Operator-backed service. However, `odo` version 3 currently only supports connecting to services backed by Operators that are considered bindable by the Service Binding Operator. | |
Work without a running application:: Compared to v2, the `odo add binding` command does not require the application to be running on the cluster, making it even faster. | |
Only supports bindable Operators:: | |
The `odo link` command of v2 links an application to another application and any Operator-backed service. However, `odo` v3 currently only supports connecting to services backed by Operators that are considered bindable by the Service Binding Operator. |
The This is because your PR targets the If the update in your PR does NOT apply to version 4.13 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main. |
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 |
Only versions 4.10+ are still in maintenance. I am removing labels from earlier versions from this PR. |
The This is because your PR targets the If the update in your PR does NOT apply to version 4.14 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main. |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closed this PR. In 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/test-infra repository. |
Version(s):
4.8+
Issue:
https://issues.redhat.com/browse/RHDEVDOCS-4476
Link to docs preview:
https://51192--docspreview.netlify.app/openshift-enterprise/latest/cli_reference/developer_cli_odo/understanding-odo.html#odo-features_understanding-odo
https://51192--docspreview.netlify.app/openshift-enterprise/latest/cli_reference/developer_cli_odo/understanding-odo.html#odo-new-commands-30_understanding-odo
QE review: