Skip to content

v0.1.0
Compare
Choose a tag to compare
@dgolovin dgolovin released this 19 Sep 06:48
v0.1.0
b4b1cc4
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

WARNING !!! Breaking Changes

This release 0.1.0 contains breaking changes mentioned below.

  • The Components created with previous versions will no longer be visible in OpenShift Application Explorer view.
  • The Extension will prompt the user to specify the context folder when creating new Components and then add selected folder to workspace.
  • New Component, Url and Storage objects are created locally in context folder and not immediatly pushed to the cluster.

Please follow the migration guide to resolve any possible issues.

In case of any queries, please use the Feedback & Question section.

Added

  • Every component and service required to have a context folder. The extension will prompt the user to specify the context folder when creating component or service.
  • The selected context folder will be added to the current vscode workspace.
  • New Component command creates a local component configuration ./.odo/config.yaml withing the context folder selected, nothing is created in the cluster at this point.
  • All component configuration is 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 to previously deployed component, run Push command for the component from component's context menu or command palette.
    • Push command will create component, component's urls and storage on the OpenShift cluster and push your local source files to it.
  • Import actions for components which were created using old versions of the extension.
  • Support for OpenShift 4.x clusters.
  • New Commands on OpenShift Application Explorer View Title
    • Switch Contexts - This will help users to switch contexts from kubeconfig.
    • Report an Issue - Users can directly file extension issues/feedback.
  • New Commands in in Kubernetes Clusters View for OpenShift specific resources
    • For BuildConfig
      • Start Build
      • Rebuild
      • Show Logs
      • Follow Logs
    • For DeploymentConfig
      • Deploy
      • Show Logs
    • Open in Console for k8s resources in Kubernetes View.

Changes

  • The OpenShift labels used internally by odo to identify its components, have been updated to match https://github.com/gorkem/app-labels/blob/master/labels-annotation-for-openshift.adoc.
  • Components can be in 3 states:
    • pushed - the components are deployed into the cluster.
    • not pushed - the components are in local config but NOT deployed into the cluster.
    • no context - there is no context folder associated with the component in the workspace.
  • Extension uses odo-v1.0.0-beta5.
  • Clusters view removed from OpenShift Views Container. Users can perform all the required action from Kubernetes extension Clusters view.
Assets 3
Loading