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

Commit

Permalink
Update readme with note about current status
Browse files Browse the repository at this point in the history
  • Loading branch information
paulbatum authored Oct 14, 2019
1 parent f8eee6c commit 104c76e
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,10 @@ Fully featured IoT Hub input and output bindings to Azure IoT Hub, allowing comm
* Set Device Twin: output binding that updates desired properties of specified device from Azure Functions
* Get Device Twin: input binding that gets device twin of the specified device once the Function's trigger is fired

#### Current Status

This extension is still in the prototype phase and has not been published to NuGet. If you need to process IOT Hub messages with Azure Functions, the currently supported method is documented [here](https://docs.microsoft.com/en-us/samples/azure-samples/functions-js-iot-hub-processing/processing-data-from-iot-hub-with-azure-functions/).

#### Example

##### Cloud to Device
Expand Down Expand Up @@ -73,4 +77,4 @@ This project is under the benevolent umbrella of the [.NET Foundation](http://ww

## Contributing

This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.

0 comments on commit 104c76e

Please sign in to comment.