From 83698d071ed4db2b794710eeebad49edd074166c Mon Sep 17 00:00:00 2001 From: Yana Hontyk Date: Tue, 7 Apr 2020 12:18:00 +0200 Subject: [PATCH] odo release notes 4.4 --- .../odo-release-notes.adoc | 104 ++++++++++-------- .../openshift-developer-cli-attributes.adoc | 2 +- 2 files changed, 60 insertions(+), 46 deletions(-) diff --git a/cli_reference/openshift_developer_cli/odo-release-notes.adoc b/cli_reference/openshift_developer_cli/odo-release-notes.adoc index 1f33627ff9..6ad7637000 100644 --- a/cli_reference/openshift_developer_cli/odo-release-notes.adoc +++ b/cli_reference/openshift_developer_cli/odo-release-notes.adoc @@ -6,32 +6,48 @@ include::modules/common-attributes.adoc[] toc::[] [id="odo-notable-improvements_{context}"] -== Notable improvements in `{odo-title}`{nbsp}{odo-ver} +== Notable changes and improvements in `{odo-title}`{nbsp}{odo-ver} -* IBM Z and PowerPC architecture binaries are now available. -* `odo catalog` has been improved to provide more useful output information. -* Information prompts have been added to the `odo service create` command, providing possible next step scenarios. -* Log verbosity can now be set with an environment variable `ODO_LOG_LEVEL`. -* Use `odo preference set PushTimeout ` to specify the number of seconds `odo` waits for a component Pod to be deployed before the command fails. -* Overall documentation improvements. The documentation now includes a description of `{odo-title}`'s inner architecture. +* A `--now` flag is added for `odo create`, `odo url`, and `odo config`. ++ +Run `odo url create --now` to create the URL in the configuration and propagate all the changes to the cluster. +* An `odo debug info` command is added. The command displays if the debug mode is enabled for a component, if the port-forward process is running, and information about ports used. +* The `odo push` output now shows the exact error from the OpenShift cluster on failure. ++ +* A `--secure` flag is added for `odo url`. It indicates whether a URL is secure. +* `odo storage list` now displays the information about the storage state: `Pushed`, `NotPushed` or `Locally Deleted`. +* `odo debug port-forward` now selects a port automatically if the default port (5858) is occupied. +* The `--all` flag is renamed to `--all-apps`. +* The default PVC size has been increased to 10GiB. +* The JSON output for `odo storage list -o json` has been restructured. +* `nodejs-8` and `nodejs-10` images are no longer supported. +* Experimental mode feature. By default, features under development or in experimental mode are hidden from the user. ++ +** To enable experimental mode, run: ++ +---- +$ odo config set --env ODO_EXPERIMENTAL=true +---- ++ +or ++ +---- +$ odo preference set experimental true +---- +** To disable experimental mode, run: ++ +---- +$ odo config unset --env ODO_EXPERIMENTAL +---- ++ +or ++ +---- +$ odo preference set experimental false +---- -//// +* `{odo-title}` now supports Ingress to create URLs on Kubernetes. -= Notable features in odo for the OCP 4.2 release - -`{odo-title}`{nbsp}{odo-ver} offers a simple way to develop applications on {product-title}. `{odo-title}` is completely client-based and requires no server within {product-title} cluster. - -`{odo-title}`{nbsp}{odo-ver} comes with: - -* Simple syntax and design centered around concepts familiar to developers such as projects, applications and components. -* Compatibility with any language or runtime within the OpenShift catalog of component types. -* Capability to add custom component types using custom image builders. -* Official support for Java and Node.js component types. -* Service catalog which allows users to connect applications deployed on {product-title} cluster to the Template Service Broker. -* `odo service create` - an interactive mode which guides users through the process of creating applications. -* `odo watch` - a feature that automatically detects changes to local code and applies the changes to the component in real time. - -//// [id="odo-getting-support_{context}"] == Getting support @@ -42,36 +58,23 @@ If you find an error or have suggestions for improving the documentation, file a .For Product -If you find an error, encountered a bug, or have suggestions for improving the functionality of `{odo-title}`, file an issue in link:http://bugzilla.redhat.com[Bugzilla]. Choose the *Red Hat odo for {product-title}* product type. +If you find an error, encounter a bug, or have suggestions for improving the functionality of `{odo-title}`, file an issue in link:http://bugzilla.redhat.com[Bugzilla]. Choose the *Red Hat {odo-title} for {product-title}* product type. Provide as many details in the issue description as possible. [id="odo-fixed-issues_{context}"] == Fixed issues -* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760573[Bug 1760573] The active pointer does not switch to the current active project after the deletion of a project. +* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760575[Bug 1760575] The `odo app delete` command removes application components but not Services. -* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760578[Bug 1760578] The `odo watch` command does not fail with an error message for Git-based components, but it should. +* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760577[Bug 1760577] The `odo push` command does not delete the OpenShift objects when the component name is changed. -* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760583[Bug 1760583] The `odo config unset` command does not unset an environment variable, but says it did. - -* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760585[Bug 1760585] The `odo delete --all` command deletes the `$HOME/.odo` folder when run from `$HOME`. - -* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760589[Bug 1760589] Autocompletion does not work for the `--context` flag in `odo push`. - -* link:https://bugzilla.redhat.com/show_bug.cgi?id=1761442[Bug 1761442] The `component create` command fails when used with the `--context` flag and `--binary` flag if the binary is located in a temporary folder. - -* link:https://bugzilla.redhat.com/show_bug.cgi?id=1783179[Bug 1783179] When you set an environment variable, create a URL route, and then change the source code of the component, the URL route becomes inaccessible. [id="odo-known-issues_{context}"] == Known issues * link:https://bugzilla.redhat.com/show_bug.cgi?id=1760574[Bug 1760574] A deleted namespace is listed in the `odo project get` command. -* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760575[Bug 1760575] The `odo app delete` command removes application components but not Services. - -* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760577[Bug 1760577] The `odo push` command does not delete the OpenShift objects when the component name is changed. - * link:https://bugzilla.redhat.com/show_bug.cgi?id=1760586[Bug 1760586] The `odo delete` command starts an infinite loop after a project is deleted and a component name is set. * link:https://bugzilla.redhat.com/show_bug.cgi?id=1760588[Bug 1760588] The `odo service create` command crashes when run in Cygwin. @@ -82,14 +85,25 @@ Provide as many details in the issue description as possible. * link:https://bugzilla.redhat.com/show_bug.cgi?id=1761440[Bug 1761440] It is not possible to create two Services of the same type in one project. -[id="odo-technology-preview_{context}"] -== Technology Preview features in `{odo-title}`{nbsp}{odo-ver} +* link:https://bugzilla.redhat.com/show_bug.cgi?id=1821643[Bug 1821643] `odo push` does not work on the .NET component tag 2.1+. ++ +Workaround: specify your .NET project file by running: ++ +---- +$ odo config set --env DOTNET_STARTUP_PROJECT= +---- -`odo debug` is a feature that allows users to attach a local debugger to a component running in the Pod on {product-title}. +[id="odo-technology-preview_{context}"] +== Technology Preview features `{odo-title}` in `{odo-title}`{nbsp}{odo-ver} + +* `odo debug` is a feature that allows users to attach a local debugger to a component running in the Pod. To learn more, see xref:../../cli_reference/openshift_developer_cli/debugging-applications-in-odo.adoc#debugging-an-application_debugging-applications-in-odo[Debugging applications in odo] :FeatureName: odo debug include::modules/technology-preview.adoc[leveloffset=+1] -- Use the `odo debug port-forward` command to start port forwarding. -- Use the `odo config set DebugPort 9292` command to specify the remote port that the debugging agent should run on. -- Use the `odo debug port-forward --local-port 9292` command to specify the local port for port forwarding. \ No newline at end of file +* Devfile support. You can now create and deploy your applications using the devfiles with `{odo-title}`. A devfile is a file that defines the development environment: environment variables, image, and so on. To access this feature, you must enable experimental mode with `odo preference set experimental true`. ++ +To see the list of currently supported devfile components, run `odo catalog list components` + +:FeatureName: Devfile support +include::modules/technology-preview.adoc[leveloffset=+1] diff --git a/modules/openshift-developer-cli-attributes.adoc b/modules/openshift-developer-cli-attributes.adoc index dc95daa51c..f70966e86e 100644 --- a/modules/openshift-developer-cli-attributes.adoc +++ b/modules/openshift-developer-cli-attributes.adoc @@ -1,3 +1,3 @@ :odo-title-full: OpenShift Do :odo-title: odo -:odo-ver: 1.1.0 \ No newline at end of file +:odo-ver: 1.1.2