- Updated dependencies / package vulnerabilities.
- Version bump for non-preview release.
- Changed D2C messages to always declare message content-type as
application/json
and encoding asutf-8
- Updated package vulnerabilities
- Updated package vulnerabilities
- Migrated testing framework from
vscode
->vscode-test
- Updated package vulnerabilities
- Regression in handling of connecting to underlying Event Hub
- Handling of JSON formatted D2C messages by adding contentType and contentEncoding (issue 440)
- Multiple NPM package updates for connecting to Azure resources.
- Multiple NPM package updates to resolve vulnerabilities
- Plug and Play interfaces node from device tree view
- Support monitoring Event Hub messages in different regions
- Adopt VS Code's 'asWebviewUri' API
- Update third party notice
- Fix Handlebars vulnerability CVE-2019-19919 (npm advisory)
- Display Azure IoT Hub name in Azure IoT Hub tree view
- Rename from 'Azure IoT Hub Toolkit' to 'Azure IoT Hub'
- Add deployment ID in output channel when deploying at scale for Azure IoT Edge
- Rename 'Monitoring C2D' to 'Receiving C2D'
- List IoT Hub Device Provisioning Service instances
- Add C# code generation for device twin (Thanks @tomaszbartoszewski!)
- #393: Error during initialize
- List PnP Interfaces in tree view
- Brand new 'Send D2C Messages' experience
- Use tooltip to show connection state
- Show running status even when module is disconnected
- Fix typo
- Update infrastructure to support localization (Thanks @matsujirushi!)
- Localization for Japanese language (Thanks @matsujirushi!)
- Expose API to read IoT Hub connection string
- Use OS credential store to store IoT Hub connection string (To be more secure, we will no longer use
azure-iot-toolkit.iotHubConnectionString
in settings.json to store IoT Hub connection string)
- Update json schema version to 2.0 for deployment validation
- #332: Bump axios from 0.18.0 to 0.18.1
- #334: The menu/icon of new Edge Device is sometimes not right
- Endpoints tree view
- Monitor custom Event Hub endpoint
- Rename 'Start Monitoring D2C Message' to 'Start Monitoring Built-in Event Endpoint'
- Show properties when monitoring C2D message
- Upgrade @azure/event-hubs npm to 2.0.0
- Fix context menu issue for deployment JSON file
- #303: 'Create Module' should not show in context menu of device node
- #293: Fix deployment JSON validation issue when create options is larger than 512 bytes
- Add JSON schema check when creating IoT Edge deployment
- Sort and group menu for device explorer
- [Accessibility] Indicate device/module status in description of tree item
- Indicate monitoring D2C message is for built-in endpoint
- Switch to VS Code built-in clipboard API to reduce extension size
- #278: Double select device ID when creating IoT Edge deployment via context menu in treeview
- Add support for Azure IoT distributed tracing (preview)
- Move 'Create Module' context menu into 'Modules' node
- Add 'Stop' button for monitoring C2D message in Status Bar
- Reorder and group context menu
- Add confirmation prompt when deleting resource
- Add 'Stop' button for monitoring D2C message in Status Bar
- Add Direct Method template for Node.js code generation
- Use Webpack to improve extension performance ⚡
- Remove 'Refresh' item from context menu
- Resolve #218: Add 'Stop Monitoring D2C Message' into context menu of explorer title
- Brand new! Rename from 'Azure IoT Toolkit' to 'Azure IoT Hub Toolkit'
- Support IoT Edge multiple platforms scenario
- Support Azure National Clouds
- Better hint user when they fail to set IoT Hub connection string
- Better hint user when loading device list failed
- Support passing JSON in payload for direct methods
- Add 'Refresh' into context menu of normal device
- Add 'Refresh' icon inline
- Resolve #189: Use Node SDK instead of REST API
- Add device twin templates for Node.js code generation
- Add configuration to enable auto refresh and set refresh interval (@tomaszbartoszewski: #184)
- Display friendly info when no subscriptions are available (@tomaszbartoszewski: #174)
- Use sans-serif font for welcome page on Linux and macOS (@tomaszbartoszewski: #176)
- Get module info
- Copy module connection string
- Add F# code generation for device to cloud communication (@tomaszbartoszewski: #172)
- Valid that expiration time should be a number when generating SAS token (@tomaszbartoszewski: #173)
- Keep input box open when entering D2C message (@tomaszbartoszewski: #173)
- Support Module direct method
- Show Module id when monitoring D2C message
- Let user input the priority for IoT Edge deployment
- Support passing subscriptionId and resourceGroupName to createIoTHub API
- Support passing subscriptionId to selectIoTHub API
- Generate Code for C#, Go, Java, PHP or Ruby
- Module Management (List, Create, Delete module)
- Add configuration to set start time for monitoring D2C message
- Support creating IoT Hub with basic tier
- Generate Code for Node.js, Python or REST API
- Show Module Identities for IoT Edge device
- Allow
*
for target condition of IoT Edge device deployment
- Update vscode-extension-telemetry npm to latest version (0.0.18)
- Generate SAS Token for IoT Hub
- Generate SAS Token for Device
- Create Deployment for IoT Edge Device at Scale
- Add welcome page
- Add wiki page
- #92: Invoke Direct Method will fail when device name contains’#’
- Add CodeLens to update Device Twin and Module Twin
- Show warning message when user selects deployment.template.json to do deployment
- Remove iotedgectl related commands which are retired in IoT Edge GA
- Add command for updating Module Twin
- Update dependent npm to fix security vulnerability
- Fix #89: Could not create device when device id contains '#'
- URI-encoding for device id in HTTP requests: Could not list Moudles, get Module Twin and create deployment for IoT Edge device when device id contains '#'
- Add 'Azure' to command category
- Improve wording to align with Azure IoT Edge extension
- Upgrade 'ms-rest' and 'ms-rest-azure' npm to resolve security issue in moment.js
- Fix #83: Add retry logic for listing IoT Hub to work around showQuickPick issue
- Expose APIs for dependent extensions to use
- Return IoT Hub Connection String in create/select IoT Hub APIs
- Use Output Channel for showing output
- Add iotHubConnectionString parameter in create/select device APIs
- Add outputChannel parameter in create/select IoT Hub and create/select device APIs
- Show default command items ("Set IoT Hub Connection String", "Select IoT Hub") in device tree when IoT Hub Connection String is not set
- Create Edge deployment via file
- Always refresh device tree after creating IoT Hub
- Improve SKU naming
- Only list filtered subscriptions
- Sort commands in View title menu
- Not show Connection String Input Box on startup
- Rename explorer to 'Azure IoT Hub Devices'
- Move Edge code snippets to Azure IoT Edge extension
- The "Generate Edge deployment manifest" command is replaced by Azure IoT Edge extension's "Generate IoT Edge deployment manifest file" command
- [Added] Create IoT Hub
- [Added] Create Edge device
- [Added] Show different icons for Edge devices
- [Added] Command to log in to container registry for Edge
- [Added] Code snippet for Edge module and route authoring
- [Added] List Edge Modules
- [Added] View Module Twin
- [Added] Add Command Palette integration for several commands
- [Fixed] Stop monitoring D2C message and show friendly message when there is error
- [Fixed] Handle terminal closed
- [Fixed] Set eventHubClient as null when there is error
- [Added] Add support for IoT Edge
- [Added] Monitor D2C message per device
- [Changed] Show application properties when monitoring D2C message
- [Changed] Show device id when monitoring D2C message
- [Changed] Sort devices by device id in device tree
- [Added] Select IoT Hub with Azure login
- [Added] Copy connection string
- [Changed] Refresh device list right after device is created or deleted
- [Changed] Show error message in device tree explorer instead of pop-up when failing to list devices
- Add option to hide Connection String Input Box and IoT Hub info
- Show IoT Hub info when user does not enter connection string
- Handle the case when user enters an invalid connection string
- Context menu to set IoT Hub Connection String
- Improve wording for 'Monitoring stopped'
- Add 'Azure' category
- Handle devices with X.509 cert
- Migrate as official extension
- Invoke Direct Method
- Get/update Device Twin
- Remove IoT Hub commands from editor context menu
- Make stringifying D2C messages optional
- Show different icon for connected devices
- Add 'Send/monitor C2D message' into context menu of Device Explorer
- Device Explorer
- Code snippet for Direct Methods
- Send/monitor C2D message
- Code snippet for C2D message
- JavaScript code snippet to send/monitor D2C message
- Show verbose info when monitoring messages
- Output refinement for JSON object
- Send messages to Azure Event Hub
- Monitor Event Hub messages
- Show detailed info when listing devices
- Deploy and run in remote machine
- Include device-discovery-cli into extension
- Add instruction if device-discovery-cli is not installed
- Discover Ethernet, USB serial, WiFi devices
- Device management (List, Create, Delete)
- Send messages to Azure IoT Hub
- Monitor device-to-cloud messages