diff --git a/cli_reference/developer_cli_odo/odo-release-notes.html b/cli_reference/developer_cli_odo/odo-release-notes.html deleted file mode 100644 index 24925ef75c..0000000000 --- a/cli_reference/developer_cli_odo/odo-release-notes.html +++ /dev/null @@ -1,677 +0,0 @@ - - - - - - - - -odo release notes - - - - - -
-
-
- -
-
-
-

Notable changes and improvements in odo

-
-
-
    -
  • -

    The --devfile flag is added to odo create. Run odo create <component name> --devfile <devfile path> to specify your devfile location. This flag is only available in the Experimental Mode. See, Technology Preview features to learn how to enable it.

    -
    • -
  • -

    Dynamic registry support. Now you can configure your own registries with the following commands:

    -
    -
    -
    # Add registry to the registry list
-odo registry add <registry name> <registry URL>
-
-# List registry in the registry list
-odo registry list
-
-# Delete registry from the registry list
-odo registry delete <registry name>
-
-# Update registry in the registry list
-odo registry update <registry name> <registry URL>
-
-# List component with corresponding registry
-odo catalog list components
-
-# Create component that is hosted by specific registry
-odo create <component type> --registry <registry name>
    -
    -
    -
    • -
  • -

    The --starter flag is added to odo create. Run odo create nodejs --starter <project-name> to download a source code of a project specified in the devfile. If no project name is specified, odo downloads the first one.

    -
    • -
  • -

    The --context flag is added to odo push. With --context you can trigger odo push from outside the source code directory. Run odo push --devfile <path to the devfile> --context <directory with your component> to specify the directory of your component.

    -
    • -
  • -

    Performance improvement for odo catalog list components when using the devfiles.

    -
    • -
  • -

    The --now flag is added for odo url delete when using the devfiles.

    -
    • -
  • -

    odo url delete --now now works with the devfiles.

    -
    • -
  • -

    The --debug flag now works with the devfiles.

    -
    • -
  • -

    Added machine readable output for listing Operator backed services. Run odo catalog list services -o json to display information about Operators and services in a JSON format.

    -
    • -
  • -

    Added machine readable output for debugging. Run odo debug info -o json to display the debugging information in a JSON format.

    -
    • -
  • -

    Added machine readable output for odo push. Run odo push -o json to display event notifications in a JSON format.

    -
    • -
-
-
-
-
-

Getting support

-
-
-
For Documentation
-

If you find an error or have suggestions for improving the documentation, file an issue in Bugzilla. Choose the {product-title} product type and the Documentation component type.

-
-
-
For Product
-

If you find an error, encounter a bug, or have suggestions for improving the functionality of odo, file an issue in Bugzilla. Choose the Red Hat odo for {product-title} product type.

-
-
-

Provide as many details in the issue description as possible.

-
-
-
-
-

Known issues

-
-
-
    -
  • -

    Bug 1760574 A deleted namespace is listed in the odo project get command.

    -
    • -
  • -

    Bug 1760586 The odo delete command starts an infinite loop after a project is deleted and a component name is set.

    -
    • -
  • -

    Bug 1760588 The odo service create command crashes when run in Cygwin.

    -
    • -
  • -

    Bug 1760590 In Git BASH for Windows, the odo login -u developer command does not hide a typed password when requested.

    -
    • -
  • -

    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.

    -
    • -
  • -

    Bug 1761440 It is not possible to create two Services of the same type in one project.

    -
    • -
  • -

    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=<path to your project file>
    -
    -
    -
    • -
-
-
-
-
-

Technology Preview features odo

-
-
-
    -
  • -

    odo debug is a feature that allows users to attach a local debugger to a component running in the Pod. -To learn more, see Debugging applications in odo

    -
    • -
-
-
- - - - - -
-Important - -
-

odo debug is a Technology Preview feature only. Technology Preview features -are not supported with Red Hat production service level agreements (SLAs) and -might not be functionally complete. Red Hat does not recommend using them -in production. These features provide early access to upcoming product -features, enabling customers to test functionality and provide feedback during -the development process.

-
-
-

For more information about the support scope of Red Hat Technology Preview -features, see https://access.redhat.com/support/offerings/techpreview/.

-
-
-
-
-
    -
  • -

    Devfile support. With odo, you can create and deploy your applications using the devfiles. To learn more, see Creating applications by using devfiles. 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.

    -
    -
    • -
-
-
- - - - - -
-Important - -
-

Devfile support is a Technology Preview feature only. Technology Preview features -are not supported with Red Hat production service level agreements (SLAs) and -might not be functionally complete. Red Hat does not recommend using them -in production. These features provide early access to upcoming product -features, enabling customers to test functionality and provide feedback during -the development process.

-
-
-

For more information about the support scope of Red Hat Technology Preview -features, see https://access.redhat.com/support/offerings/techpreview/.

-
-
-
-
-
    -
  • -

    Operators support. You can now create services from Operators with odo. To learn more, see Creating instances of services managed by Operators 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.

    -
    -
    • -
-
-
- - - - - -
-Important - -
-

Operators support is a Technology Preview feature only. Technology Preview features -are not supported with Red Hat production service level agreements (SLAs) and -might not be functionally complete. Red Hat does not recommend using them -in production. These features provide early access to upcoming product -features, enabling customers to test functionality and provide feedback during -the development process.

-
-
-

For more information about the support scope of Red Hat Technology Preview -features, see https://access.redhat.com/support/offerings/techpreview/.

-
-
-
-
-
-
- - - \ No newline at end of file diff --git a/modules/developer-cli-odo-creating-and-deploying-a-nodejs-application-with-odo.adoc b/modules/developer-cli-odo-creating-and-deploying-a-nodejs-application-with-odo.adoc index c767513389..daf4b22b1a 100644 --- a/modules/developer-cli-odo-creating-and-deploying-a-nodejs-application-with-odo.adoc +++ b/modules/developer-cli-odo-creating-and-deploying-a-nodejs-application-with-odo.adoc @@ -22,7 +22,7 @@ ifdef::single[] + [source,terminal] ---- -$ mkdir my_components $$ cd my_components +$ mkdir my_components && cd my_components ---- . Download the example Node.js application: diff --git a/modules/developer-cli-odo-deploying-the-back-end-component.adoc b/modules/developer-cli-odo-deploying-the-back-end-component.adoc index e391120345..6e9331784e 100644 --- a/modules/developer-cli-odo-deploying-the-back-end-component.adoc +++ b/modules/developer-cli-odo-deploying-the-back-end-component.adoc @@ -45,7 +45,7 @@ openjdk18 myproject latest + [source,terminal] ---- -$ mkdir my_components $$ cd my_components +$ mkdir my_components && cd my_components ---- . Download the example back-end application: