Support for azurerm_data_factory_integration_runtime_self_hosted

[pearcec]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

See the link below. In an enterprise environment it is common to have a bare shared integration runtime. This resource would create the linkage. Hopefully the testing won't require an actual IR and we can pass in a fake.

New or Affected Resource(s)

• azurerm_data_factory_integration_self_hosted

Potential Terraform Configuration

resource "azurerm_data_factory_integration_runtime_self_hosted" "host" {
  name                = "host" 
  resource_group_name = "shared-rg"
  data_factory_name   = "shared-df"
  description         = "" # (optional)
}

# linked self-hosted DF identity needs Contributor access

resource "azurerm_data_factory_integration_runtime_self_hosted" "ir" {
  name                = "ir" 
  resource_group_name = "rg"
  data_factory_name   = "df"
  description         = "" # (optional)
  rbac_authentication {
    resource_id       = azurerm_data_factory_integration_runtime_self_hosted.host.id
  }
}

The ir name has the following validate: ^[A-Za-z0-9]+(?:-[A-Za-z0-9]+)*$

The code and final names is still a WIP.

References

• https://azure.microsoft.com/en-us/blog/sharing-a-self-hosted-integration-runtime-infrastructure-with-multiple-data-factories/
• https://docs.microsoft.com/en-us/rest/api/datafactory/integrationruntimes/createlinkedintegrationruntime
• https://docs.microsoft.com/en-us/rest/api/datafactory/integrationruntimes/createorupdate#linkedintegrationruntimerbacauthorization

[markti]

@pearcec do we need a separate resource for linkedInfo? It appears that linkedInfo will always have a 1-1 relationship with a SelfHostedIntegrationRuntime. In that case, I'd suggest flattening it and putting the linkedInfo properties (key / rbac) directly on the SelfHostedRuntime.

[pearcec]

key_authorization use is indeterminate. Received vague error and found no explanation of use in docs, or powershell calls.

{"error":{"code":"InvalidSharingIntegrationRuntimeOperation","message":"The administrative operation on shared integration runtime is not allowed via linked integration runtime 'acctestirs ht200417164656073154'. Error message: The payload is not valid for RBAC authorization. The actual authorization type is 'Key'..","target":null,"details":null}}

[katbyte]

closed by #6503

[ghost]

This has been released in version 2.15.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.15.0"
}
# ... other configuration ...

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!