v0.1.3

This release adds OpenShift: Debug command for local Java and Node.js components. The command is available form command palette and OpenShift Application Explorer View context menu for nodes representing Components. See issues #1322 and #1328 for details.

It also includes update for OpenShift Do CLI. Version 1.0.2 will be downloaded after extension is updated to this release.

v0.1.2

This release brings to you:

• #1277 Latest v1.0.1 version of OpenShift Do CLI tool
• #1268 New OpenShift: Create command to create resources based on file from active editor
• Bugfixes for minor issues:
  • #1262 Keep QuickInputs open after VSCode window lost focus
  • #1261 'Unlink' command for components does not work
  • #1247 Open console command doesn't open the console web page
  • #1260 Sometimes login does not work anymore
  • #1284 With latest VSCode 1.40.0 release oc and odo download fails on sha256 verification

v0.1.1 - 🎃Trick or Treat

Halloween Release 🎃

This release is built on top of 0.1.0. If any developer is migrating from <=0.0.23 release, please follow the Migration Guide.

Updates

• Extension uses OpenShift Do(odo) 1.0.0 GA
• Support Red Hat Code Ready Containers 1.0 for OpenShift 4.x clusters
• Update download path for odo-v1.0.0 binary
• Icons for OpenShift Connector are working for Eclipse Che extension
• Demo video and blog updated for 0.1.1 release

Changes

• #1254 use vscode open command instead of open module for external links
• #1236 Show progress bar for credentials and token Login
• #1229 support deep nesting for binary files
• #1243 remove flags from storage commands
• #1211 Add json output for catalog list services
• #1213 Added json output for catalog list components to determine component type and version
• #1218 Provide information message to user to Push the components after success of component creation
• Increase Code Coverage and improve unit tests

v0.1.0

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.

v0.0.23

• #920 Fix odo CLI tool download checksum fail for all 3 OS variants
• #903 Add new login experience using k8 config
• #901 Fix for Deleting interlinked components breaks the application
• #911 Integrate Azure Pipelines to CI builds
• Move public chat discussion to gitter

v0.0.22

• #888 Prettify json in OpenShift Output Channel
• #882 Add BuildConfig and Builds to Clusters View
• #835 Provide keybinding for Login, push and refresh commands
• #873 Hide session token when used for log in to the cluster

v0.0.21

• Added dependency to Kubernetes extension from Microsoft
• Extend Kubernetes Clusters tree view
  • #853 Show OpenShift icon for OpenShift clusters
  • #851 Show OpenShift resources
    • Projects
    • Templates
    • Deployment Configs under Workloads node
    • Image Streams under Workloads node
    • Routes under Network node
  • #852 Add Use Project command for switching between Projects
• Added Kubernetes Clusters view back to the OpenShift views container

v0.0.20

• URL management for a component in Application Explorer
  • Showcase URL names as child nodes inside a component in Application Explorer
  • Allow Delete and Open in Browser for an individual URL
  • Display hostname and port information when selecting the URL to open in browser
• Add OpenShift Connector: Output verbosity level setting. This helps to configure Output verbosity level (value between 0 and 9) for OpenShift Create, Push and Watch commands in output channel and terminal view
• Remove deprecated opn module with open npm module
• Nodes are sorted alphabetically in Explorer view
• .vsix files are added to the release builds

Install from Visual Studio Marketplace or download binaries published below and use Install from VSX... command in Microsoft Visual Studio Code command palette.

v0.0.19

update readme with latest gif

v0.0.18

Changes:

• Update to use odo v0.0.20
• Support reference option for creating components from git repository
• Add feature to store passwords in Credential Manager
• Use '-wait' flag when creating service to wait until it is provisioned
• Add OpenShift: Show Output Channel to command palette
• Allow user to directly create components with 3 different options using command palette
• Split OpenShift: Login into Cluster to two commands

Install from Visual Studio Marketplace or download binaries published below and use Install from VSX... command in Microsoft Visual Studio Code command palette.