Skip to content
This repository has been archived by the owner on Nov 12, 2024. It is now read-only.

Latest commit

 

History

History
264 lines (180 loc) · 12 KB

CHANGELOG.md

File metadata and controls

264 lines (180 loc) · 12 KB
Raw

Change Log

All notable changes to the "vscode-camelk" extension will be documented in this file.

0.0.42

  • Update default runtime version to v2.3.3

0.0.41

  • Update Red Hat telemetry dependency to reduce number of event sent (startup information will be sent one time per day per user)

0.0.40

  • Fix regression for command to create Secrets
  • Update default runtime version to v2.3.1

0.0.39

  • Update default runtime version to v2.3.0
  • Avoid creating .camel.jbang folder at workspace root when the extension is starting

0.0.38

  • Update default runtime version to v2.2.0

0.0.37

  • Fix Java standalone support on MacOS

0.0.36

  • Requires jbang for java standalone completion. It allows also to get rid of internal dependency to kamel local which is removed from kamel 2.x.
  • Fix Java standalone support on Windows
  • Update default runtime version to v2.1.0
  • Removal of Start integration with resources command as Camel K 2.1 is no more supporting it with files (which was the only implemented use case)

0.0.35

  • Support *.yml Camel files (and not only *.yaml)
  • Remove Create Integration file command, in favor of Camel: Create Camel Route in xxx DSL provided by VS Code Language Support for Apache Camel. It allows also to get rid of internal dependency to kamel init which is removed from kamel 2.x.
  • Remove completion for traits in VS Code tasks.json. This will be now provided by the VS Code Language Support for Camel extension. It allows also to get rid of internal dependency to kamel help trait which is removed from kamel 2.x.

0.0.34

  • Update default runtime version to v1.12.1
  • Rename command Start Apache Camel K Integration to Deploy Integration with Apache Camel K
  • Provide Quick menu action on editor title to Deploy Integration with Apache Camel K

0.0.33

  • Update default runtime version to v1.11.0

0.0.32

  • Update default runtime version to v1.10.0
  • Removed Didact extension support
  • Added the following extensions as dependencies. They are now installed automatically when installing VS Code Camel K instead of being optional downloads.

0.0.31

  • Update default runtime version to v1.9.2

0.0.30

  • Update default runtime version to v1.8.2

0.0.29

  • Update default runtime version to v1.8.1
  • Update default Yaml schema to Camel 3.14.1

0.0.28

  • Update default runtime version to v1.7.0
  • Update default Yaml schema to Camel 3.13.0
  • Add keyword to help discovery with Camel yaml dsl

0.0.27

  • Strip ANSI from kamel log to improve display in log view which doesn't support it
  • Update default runtime version to v1.6.0

0.0.26

  • Adapt Didact tutorial registration to VS Code Didact 0.4.0 updated API
  • Update default runtime version to v1.5.0
  • Provide CodeLenses:
    • to refresh classpath dependencies on Camel K Java files containing a Camel K modeline
    • to start an integration on Camel K files using .camelk. file name pattern or containing a Camel K modeline
  • resource has been replaced by resources to allow providing several of them in Camel K VS Code Tasks
  • Actions related to starting an integration with resource, configmap, or secret now require kamel 1.5.0 community or 1.4.0 Red Hat

0.0.25

  • Debugging:
    • Provide right-click menu in Integration view to attach a Java debugger
    • Provide specific camel-k-debug VS Code tasks

0.0.24

  • Update default runtime version to v1.4.0
  • Provide command to refresh Java classpath. It allows to have dependencies declared as modeline part of classpath.
    • It requires Camel K 1.4.0
    • If mistakenly called with Camel K 1.3.2-, need to restart VS Code for basic dependencies to be available again.
    • It supports modeline dependencies notation from local build. See apache/camel-k#2213
    • A single classpath is provided. It means that refresh command needs to be called when switching between Integration file written in Java that does not have the same dependencies.
    • There is no progress indicator. Please be patient. The first time may take several minutes on a slow network.
  • Provide telemetry information when using Start Apache Camel K integration command about language of the file deployed and the kind of deployment used (basic, dev, ...)

0.0.23

  • Update default runtime version to v1.3.2

0.0.22

  • Provide opt-in telemetry to gather information on Camel K integration created through provided command and most command ids.

0.0.21

  • Update default runtime version to v1.3.1

0.0.20

  • Change default of auto-update of kamel cli binary from true to false. It avoids that Camel K regressions are breaking the extension.

0.0.19

  • Support space to path of executable kamel and kubectl. Especially useful for user name with space.
  • Update default runtime version to v1.2.1

0.0.18

  • Update default runtime version to v1.2.0

0.0.17

  • Associate Yaml Camel K schema when there is the Camel K modeline. The associated schema is configurable in the settings.
  • Update default runtime version to v1.1.1

0.0.16

  • Update default runtime version to v1.1.0
  • Fix runtime retrieval to use more of the GitHub API to determine download location via browser_download_url

0.0.15

  • Add default value for trait property when auto-completing from trait name
  • Provide description for trait completion in tasks.json
  • Update default runtime version to 1.0.1

0.0.14

  • Update default runtime version to 1.0.0
  • Listing VS Code task to deploy Camel K integration in "Start Apache Camel Integration" command
  • Completion for trait names and trait properties in tasks.json
  • Command to create new Apache Camel K Integration files
  • A tutorial to create and deploy your first Camel K Integration is available (requires VS Code Didact to be installed)
  • Access to Kit builder log has been removed. Since Camel K 1.0.0, the corresponding log is by default in the Apache Camel K Operator log

0.0.13

  • Provide tasks to support multi-arguments launch of Camel K integrations
  • Change log functionality from Output channels to separate log windows that can be moved and placed in the display
  • Add the ability to auto-scroll with a log window or turn it off so it remains at a particular location
  • Add an extension preference to close an open log window if the integration is removed
  • Add a new button to the Integrations view that opens the Apache Camel K Operator log
  • Add a new context menu to published integrations in the Integrations view to open the Kit Builder log
  • Update default runtime version to 1.0.0-RC2
  • Add a setting to override the default version to use for the Camel K cli to avoid auto-upgrades
  • Add a validation when new Camel K CLI is downloaded to verify that it is available. If not, provide error to help with diagnosis

0.0.12

  • avoid infinite loop when connection to kamel instance is not configured

0.0.11

  • Pure Java language support with standalone Camel K Java files (requires vscode-java 0.55.0 and that the file contains the word camel)
  • Upgrade default Kamel client to 1.0.0-RC1

0.0.10

  • Remove Rest Proxy functionality
  • Automatically download the kubectl and kamel CLI tools
  • Clean up underlying code to consistently call kubectl and kamel for all actions
  • Add optional namespace support
  • Update several NPM versions and fix any security vulnerabilities

0.0.9

  • Add ability to deploy integrations associated with Resource files
  • Added the Microsoft Kubernetes Tools extension as an extension dependency
  • Update to add Dev Mode option for quick deployment and instant feedback in the Apache Camel K Output Channel
  • Add support for --property
  • Add ability to define custom dependencies for an integration
  • Added support for starting integrations with the YAML file extension
  • Adding auto-refresh to update view when any integration changes are noted by kubectl

0.0.8

  • Fix regression preventing to use Commands to deploy integration

0.0.7

  • Update to naming approved by Red Hat legal
  • Adjusted Apache Camel K Integrations view to only refresh when visible
  • Adjusted Apache Camel K output channel to only become shown when updates are made

0.0.6

  • Added ability to deploy integrations with associated Kubernetes ConfigMaps or Secrets
  • Added ability to create Kubernetes ConfigMaps or Secrets
  • Began migrating away from direct Kubectl calls in favor of using the Kubernetes API component
  • Changed 'Camel-K' to 'Apache Camel K' across the board for consistency
  • Added tests for ConfigMap and Secret utilities
  • Added Kotlin
  • Moved menus to separate group to avoid cluttering up the Explorer context menu as much

0.0.5

  • Added status bar indicators when Camel-K integrations view is refreshing and during other events
  • Added test for kebab case based on Camel-K go test
  • Added check to see if the kamel executable is available when not using proxy
  • Fixed issue with right-click menu not correctly finding selected file
  • Added decorators to indicate state of published integration (Running is green, anything else is red)
  • Added new setting to turn off status bar messages

0.0.4

  • Added Camel-K Integration Settings where users can specify the proxy url and namespace to use the Kubernetes Rest APIs instead of the local 'kubectl' utility.
  • Added a 'Use Proxy' setting that currently enables the Camel-K Integrations view to use the Rest API instead of 'kubectl.' See the list of issues for current limitations with this code.
  • Added work-in-progress 'CamelKJSONUtils' to start building a library of functions that will enable us to package, start, and stop integrations via the Kubernetes Rest APIs. Also added a few tests to start testing those functions, though currently only the createCamelKRestURL is used.
  • Added ability to 'remove' an integration when Use Proxy is specified (using a DELETE rest API call through Kubernetes)
  • Added ability to 'refresh' the integrations view when Use Proxy is specified (using a GET rest API call through Kubernetes)
  • Removed "Stop Camel-K Integration" menu, since it duplicates the "Remove Integration" menu on the integrations view
  • Removed the streaming data from all integrations started in the VS Code workspace in favor of adding a "View log snapshot" menu for running integrations that opens a new Output channel and shows the Camel log up to that moment. This works for both proxied and local executable methods
  • reduce size of extension by moving test dependencies to devDependencies

0.0.3

  • Streamlined menus to two -- Start Camel-K Integration and Stop Camel-K Integration - to avoid duplication
  • Updated readme to include details about showing the Camel-K output channel
  • Fixed refresh so that it attempts a few times before failing, which should give deploying integrations time to come up

0.0.2

  • Fix issue with readme image and add list of current issues with github links

0.0.1

  • Initial commit of extension that provides simple menu to call kamel run --dev "selectedfile"
  • Added PR from Zoran adding a 'Stop Camel-K integration' menu
  • Added new "Camel-K Integrations" view with refresh (view action) and remove (context action)
  • Improved other actions so view is refreshed when integrations are started and stopped
  • Added support for XML files as well as Groovy and cleaned up some code
  • Cleaned up the readme and added Minikube/Camel-K install directions
  • Added Java support, though we are unable to add Java integrations at this time - details in Readme issues section
  • Fixed issue with Java integrations and now call 'kamel' from the parent directory of the integration file
  • Starting and stopping integrations now works for .java, .groovy, and .xml files
  • Updated icon used for tree elements
  • Added first test mocking adding an integration to the view
  • Added tests for the Integration view and did some code cleanup on CamelKNodeProvider