Top / Microsoft Azure / Azure Stream Analytics / Stream Input Iothub

Azure Stream Analytics Stream Input Iothub

This page shows how to write Terraform and Azure Resource Manager for Stream Analytics Stream Input Iothub and write them securely.

terraform-logo

Review your .tf file for Azure best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).

azurerm_stream_analytics_stream_input_iothub (Terraform)

The Stream Input Iothub in Stream Analytics can be configured in Terraform with the resource name azurerm_stream_analytics_stream_input_iothub. The following sections describe 4 examples of how to use the resource and its parameters.

Example Usage from GitHub

main.tf#L7
resource "azurerm_stream_analytics_stream_input_iothub" "this" {
  endpoint                     = var.endpoint
  eventhub_consumer_group_name = var.eventhub_consumer_group_name
  iothub_namespace             = var.iothub_namespace
  name                         = var.name
  resource_group_name          = var.resource_group_name
main.tf#L7
resource "azurerm_stream_analytics_stream_input_iothub" "this" {
  endpoint                     = var.endpoint
  eventhub_consumer_group_name = var.eventhub_consumer_group_name
  iothub_namespace             = var.iothub_namespace
  name                         = var.name
  resource_group_name          = var.resource_group_name
main.tf#L83
resource "azurerm_stream_analytics_stream_input_iothub" "example" {
  name                         = "iothub"
  stream_analytics_job_name    = azurerm_stream_analytics_job.example.name
  resource_group_name          = azurerm_resource_group.this.name
  endpoint                     = "messages/events"
  eventhub_consumer_group_name = "$Default"
main.tf#L153
resource "azurerm_stream_analytics_stream_input_iothub" "iotDeployment" {
  name                         = "iothub-input"
  stream_analytics_job_name    = azurerm_stream_analytics_job.iotDeployment.name
  resource_group_name          = azurerm_stream_analytics_job.iotDeployment.resource_group_name
  endpoint                     = "messages/events"
  eventhub_consumer_group_name = "$Default"

Review your Terraform file for Azure best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).

Parameters

>> from Terraform Registry

Explanation in Terraform Registry

Manages a Stream Analytics Stream Input IoTHub.

>> from Terraform Registry

Microsoft.StreamAnalytics/streamingjobs/inputs (Azure Resource Manager)

The streamingjobs/inputs in Microsoft.StreamAnalytics can be configured in Azure Resource Manager with the resource name Microsoft.StreamAnalytics/streamingjobs/inputs. The following sections describe how to use the resource and its parameters.

Example Usage from GitHub

An example could not be found in GitHub.

Parameters

  • apiVersion required - string
  • name required - string

    The name of the input.

  • properties required
      • compression optional
          • type required - string

            Indicates the type of compression that the input uses. Required on PUT (CreateOrReplace) requests.

      • partitionKey optional - string

        partitionKey Describes a key in the input data which is used for partitioning the input data

      • serialization optional
    • type required - string

    >> from Azure Resource Manager Documentation

    The Other Related Azure Stream Analytics Resources

    Frequently asked questions

    What is Azure Stream Analytics Stream Input Iothub?

    Azure Stream Analytics Stream Input Iothub is a resource for Stream Analytics of Microsoft Azure. Settings can be wrote in Terraform.

    Where can I find the example code for the Azure Stream Analytics Stream Input Iothub?

    For Terraform, the kevinhead/azurerm, niveklabs/azurerm and JodyPetroni/Jenkins source code examples are useful. See the Terraform Example section for further details.

    security-icon

    Automate config file reviews on your commits

    Fix issues in your infrastructure as code with auto-generated patches.

    Table of Contents