Releases: redhat-developer/vscode-openshift-tools
Releases · redhat-developer/vscode-openshift-tools
v0.2.1
v0.2.0
- #1507 - Support
odo 2.0.0devfile 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
v0.1.6
- #1235 Webview to create and run single node OpenShift cluster 4.5.7 with Code Ready Containers (CRC) directly from the extension
- #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 un-deployed
- #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
v0.1.5
- #1505 Update OpenShift Do cli 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
v0.1.4
#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
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: 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
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.1release
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 Componentcommand creates a local component configuration./.odo/config.yamlwithing 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
Pushcommand for the component from component's context menu or command palette.Pushcommand will create component, component's urls and storage on the OpenShift cluster and push your local source files to it.
Importactions 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 Consolefor k8s resources in Kubernetes View.
- For BuildConfig
Changes
- The OpenShift labels used internally by
odoto 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.