[id='odo-release-notes']
= {odo-title}{nbsp}{odo-ver} release notes
include::modules/openshift-developer-cli-attributes.adoc[]
include::modules/common-attributes.adoc[]
:context: odo-release-notes
toc::[]

[id="odo-notable-improvements_{context}"]
== Notable 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 <seconds>` 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.

////

= 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

.For Documentation

If you find an error or have suggestions for improving the documentation, file an issue in link:http://bugzilla.redhat.com[Bugzilla]. Choose the *{product-title}* product type and the *Documentation* component type.

.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.

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=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=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.

* link:https://bugzilla.redhat.com/show_bug.cgi?id=1760590[Bug 1760590] In Git BASH for Windows, the `odo login -u developer` command does not hide a typed password when requested.

* link:https://bugzilla.redhat.com/show_bug.cgi?id=1783188[Bug 1783188] In a disconnected cluster, the `odo component create` command throws an error `...tag not found...` despite the component being listed in the catalog list.

* 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}

`odo debug` is a feature that allows users to attach a local debugger to a component running in the Pod on {product-title}. 

: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.