- #1966 Print CRC commands to 'CRC Logs' channel
- #1959 Telemetry should report errors without user related info
New features and bugfixes:
- #1952 Fix OpenShift icon broken image
- #1953 Update to CodeReady Containers (CRC)
1.22.0to use OpenShift4.6.15
New features and bugfixes:
- #1868 Telemetry Reporting
- #1855 Devfile Starter Projects support
- #1896 Developer Sandbox for Red Hat OpenShift
- #1907 Update to odo
2.0.4 - #1912 Update CodeReady Containers (CRC) download link to v1.21.0
Noteworthy changes:
- #1507 - Support odo 2.0.0 devfile components
- #1771 - Describe command fails for components without context
- #1773 - Expanding component w/o context in Application Explorer fails to get storage list
- #1754 - Provide RedHat OpenShift logo in 'Add OpenShift Cluster' editor for dark and light color themes
- #1751 - Run CRC webview only in VSCode and not on Che/CRW instance
- #1740 - Migrate to Red Hat CodeReady Containers
0.1.16release - #1735 - Update Start CRC Editor to match 'Try OpenShift' page
- #1731 - Use
vscode-kubernetes-tools-apiv1.2.0 - #1729 - Components without context don't show up in application explorer
- #1762 - Publish extension to open-vsx.org registry
Noteworthy changes:
- #1235
- Add webview to run CodeReady Containers (CRC)
1.15.0from extension. This allows to run a local instance of OpenShift4.5.7directly from the extension. - Add Extension Settings for CRC binary location, pull secret, optional configurations.
- Provide CRC Start/Stop/Refresh actions in the webview.
- Add webview to run CodeReady Containers (CRC)
- #1707 Add Stop CRC action in Status Bar.
- #1092 Deleting application only deletes components, not services
- #1332 Stop running 'odo debug' when component deleted or undeployed
- #1341 Starting debug twice on the same component should not be allowed
- #1559 Show resources only from current context in OpenShift Application Explorer view
- #1589 It is not easy to map commands to output in
OpenShift Outputchannel - #1596 'New Service' command fails with odo v1.2.1 because of changes in json output
- #1608 Use '--client' option when detecting tool version to avoid server requests
- #1615 Show context location in tooltip for component nodes in OpenShift Application Explorer
- #1617 Create
Watch SessionsView to provide control over running 'odo watch' commands - #1619 Create Simple
Debug SessionsView to show debug sessions started for components - #1636 Add 'OpenShift: Set Active Project' command to change project visible in Application Explorer view
- #1647 Show application and component quickpick lists when command executed from palette
- #1653 OpenShift Icon missing for cluster in Kubernetes view
- #1697 'New Component' command does not show component types for odo v1.2.5
- #1711 Update odo to v1.2.6
Noteworthy issues fixed in this release:
- #1505 Update odo to v1.2.1
- #1551 Command to migrate components created with v0.0.23 or earlier
- #1517 Configuration to switch between Terminal View and WebView based view to exec 'Show/Follow Log' and 'Describe' commands
- #1319 Use webview based editor to show or follow component's log
- #1495 Auto scrolling support in log viewer when following logs
- #1465 Support for creating 'https' URLs
- #1464
Describecommand for 'not pushed' components - #1463
New Storagecommand for 'not pushed' components - #1458
Describecommand for URLs - #1438 The "Please log in to the cluster" button also should open the Login QuickPick
- #1404 Add command to open Route URL from Kubernetes Clusters View
- #148 When executing command in terminal it should be named properly
Noteworthy changes:
- #1227 Include odo and oc binaries into extension package for all supported platforms macOS/Linux/Windows
- #1388 Update odo to latest release v1.1.0
- #1396 Allow to use compatible odo version available from PATH locations
- #1380 Absolute path should be used for commands when running in vscode terminal view
This release adds OpenShift: Debug command for Java and Node.js components. The command is available form command palette and OpenShift Application 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.
This release brings to you:
- #1277 Latest v1.0.1 version of OpenShift Do CLI tool
- #1268 New
OpenShift: Createcommand 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
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.
- Extension uses OpenShift Do(odo) 1.0.0 GA
- Support Red Hat CodeReady 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.1release
- #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
This release involves Breaking Changes !!
- Components created with previous version will no longer be identified. Therefore after extension is updated to new version(
0.1.0) all previously deployed components won't be visible in OpenShift Application View. - For older versions, here is the Migration Guide.
- Every component/service needs to have a context folder. The extension will prompt the user to specify the context folder with the creation of component/service.
- The selected context folder will reside in the vscode workspace.
Create Componentcreates a local component configuration within./.odo/config.yamlin the context folder selected, nothing is created on the cluster at this point.- 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
PUSHcommand for the component.PUSHwill create component/urls/storage on the OpenShift cluster and push your local files to it.
Importactions for components which were created using old versions of the extension.- Support for OpenShift 4.x clusters.
- Update Actions to Navigation Item
- Add Switch Contexts - This will help users to switch contexts from kubeconfig.
- Add Issue tracker - Users can directly file extension issues/feedback.
- Added Multiple Actions to Kubernetes resources in Kubernetes View.
- For Build Configs - Start Build, Rebuild, Show Logs, Follow Logs
- For Deployment Configs - Deploy, Show Logs
- Add
Open in Consolefor k8s resources in Kubernetes View.
- 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 stages:
- pushed - When the components are deployed into the cluster.
- not pushed - When are the components are in local config but NOT deployed into the cluster.
- no context - When there is no context folder associated with the component in the workspace.
- Extension uses odo-v1.0.0-beta5.
- Remove Clusters view from OpenShift Views Container. Users can perform all the required action from Kubernetes extension Clusters view.
- #1117 Import command for components without context
- #1107 Add migration for component/services deployed in active cluster
- #1169 Fix clone the git repository while creating Component
- #1158 Fix workflow for git + binary component
- #1152 Fix list of urls in Open in Browser action
- #1126 Migrarion to @types/vscode and vscode-test
- #1115 Remove recursive search from binary component selection
- #1113 Add binary file list from context folder in the quickPick
- #950 Provide context folder selection if no workspace present
- #1046 Use users home folder as current directory when deleting service.
Open in Browsercommands should show only components inpushedstateLink/Unlinkcommands and services should show only components inpushedstate- Remove circular dependencies introduced by extension context
- Differentiate between console urls for OpenShift 3.x and 4.x clusters
- #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
- #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
- Add dependency to Kubernetes extension from Microsoft
- Extend Kubernetes Clusters tree view
- 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 levelsetting. 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
opnmodule withopennpm module - Nodes are sorted alphabetically in Explorer view
.vsixfiles are added to the release builds
- Cache OpenShift Application Explorer nodes to avoid extra
odocalls - Reveal new created objects directly in the Explorer View
- Add
tags,brancheslist for a git reference within QuickPick item - Support
Open in browserwhen a component has several routes configured - Enable user to create multiple routes for a component
- Show progress for route creation for a component
- Add token to login into the cluster from oc command line
- Validation if git repository exists when creating component
- Update the icons for nodes representation for the cluster in Explorer View
- Represent component types with different icons
- Update to use
odo v0.0.20 - Support
referenceoption 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 Channelto command palette - Allow user to directly create components with 3 different options using command palette
- Split
OpenShift: Login into Clusterto two commands
- Update to use
odo v0.0.19 - Add duplicate resource name validation
- Implement
Describe Servicecommand for component - Delete a Service from an Application
- Update to use
odo v0.0.18 - Allow to create multiple components directly from workspace view
- Add few more commands(linking Service/Component) to command palette
- Add progress bar for delete operation (using
oc wait) - Show indeterminate progress bar for linking commands
- Allow extension to use
oc ^3.11.0if detected
- Provide the flexibility to use
commandsusing command palette #269 - Remove kubernetes clusters view from OpenShift Views Container
- Fix security issues with
event-streammodule #485 - Add login handling for when ~/.kube is empty
- Fix unhandled rejection errors in tests
- Increase unit tests code coverage
- Implement port selection when linking component with multiple ports
- Fix linking of components using
odo link - Add Coverage and Debug test launchers
- Add implementation of Linking component to a service or component #425
- Add support to create component with binary file #347
- Improve
pushcommand feature to show build log directly into vscode terminal #416 - Improve progress representation for long running commands #422
- Add fix to stop downloading odo/oc when cluster is down #406.
- Commands executed in vscode terminal always use odo from
~/.vs-openshiftdirectory #305 - Update packages and transitive dependencies to fix security vulnerabilities
- Add more test scenarios and improve code coverage
- Add actions to command palette
- Fixed application name creation validation
- Commands migrated from explorer view to cluster context
- Activate extension on any command execution from UI
- Add --namespace option to all oc calls invoked by 'Open in Browser'
- Use
oc v3.9.0andodo v0.0.16 - Fixed unit tests and increase code coverage
- Minor fixes in README
- Add support to Java components
- Support odo
v0.0.14with supervisord fix - Fix
create servicecommand based on odov0.0.14output changes
- Add screencast for the features and commands
- Fix missing icon path in README
- Add support for interactions with Red Hat OpenShift cluster
- Supports only local OpenShift cluster via minishift/cdk
- Allows to configure projects/applications/components/services/storages for a cluster
- Interactive developer experience