add sensor

Signed-off-by: Samhita Alla <[email protected]>

docs/integrations.md

@@ -49,13 +49,12 @@ Data is automatically marshalled and unmarshalled in and out of the plugin. User
 {py:class}`~flytekit.core.base_task.PythonTask` API defined in Flytekit.
 
 Flytekit Plugins are lazily loaded and can be released independently like libraries. We follow a convention to name the
-plugin like `flytekitplugins-*`, where * indicates the package to be integrated into Flytekit. For example
+plugin like `flytekitplugins-*`, where \* indicates the package to be integrated into Flytekit. For example
 `flytekitplugins-papermill` enables users to author Flytekit tasks using [Papermill](https://papermill.readthedocs.io/en/latest/).
 
 You can find the plugins maintained by the core Flyte team [here](https://github.com/flyteorg/flytekit/tree/master/plugins).
 :::
 
-
 ## Native Backend Plugins
 
 Native Backend Plugins are the plugins that can be executed without any external service dependencies because the compute is
@@ -83,7 +82,6 @@ orchestrated by Flyte itself, within its provisioned Kubernetes clusters.
 
 (external_service_backend_plugins)=
 
-
 ## External Service Backend Plugins
 
 As the term suggests, external service backend plugins relies on external services like
@@ -138,7 +136,6 @@ Flyte uses Kustomize to generate the the deployment configuration which can be l
 
 ::::
 
-
 ## Custom Container Tasks
 
 Because Flyte uses executable docker containers as the smallest unit of compute, you can write custom tasks with the
@@ -208,6 +205,7 @@ flytesnacks/examples/athena_plugin/index
 flytesnacks/examples/aws_batch_plugin/index
 flytesnacks/examples/hive_plugin/index
 flytesnacks/examples/mmcloud_plugin/index
+flytesnacks/examples/sensor/index
 flytesnacks/examples/snowflake_plugin/index
 flytesnacks/examples/databricks_plugin/index
 flytesnacks/examples/bigquery_plugin/index