redhat-developer/odo v1.0.0-beta1

on GitHub

Odo has reached BETA!

With the release of BETA, we also move to the OpenShift GitHub repo.

So what's new in BETA?

Enhancements

• odo component create creates a local component configuration in ./.odo/config.yaml, nothing is created on the cluster at this point.
• odo config Similarly to odo component create, will update the local component configuration, without affecting the running component.
• All component configurations are saved to ./.odo/config.yaml. You can commit this file to your repository to easily recreate component with the same configuration later, or to share it with someone else.
• To deploy the component to a cluster or to apply config changes, run odo push.

Changes to odo push

When first using odo create, odo will setup the necessary information required to push changes to the OpenShift cluster.
The first time you do odo push you will create component(s) on the OpenShift cluster and push your local files to it.
Adding --config flag to odo push will create or update a component without pushing the source code. Similarly --source flag will just push the files without applying a new configuration.

Breaking changes

• Components created with previous odo version are not compatible with this version
• odo url create - --port flag is required

Known issues

• odo push takes a long time because the component is restarted if no configuration has changed (#1633 #1488)
• .odoignore is not working on Windows (#1630)
• The component needs to be created before the service (#1602)
• odo push doesn't propagate file deletions (#1354)
• odo storage storage is not saved to the component config file (.odo/config.yaml) (#1388)