Azure / Azure/azure-rest-api-specs
HDInsight Cluster doesn't support Storage Container with Private Link
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 6k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
Per below error message from API side, seems it indicates that HDInsight Cluster doesn't support Storage Container with Private Link. But per the [azure doc](https://docs.microsoft.com/en-us/azure/hdinsight/hdinsight-restrict-public-connectivity#add-private-link-connectivity-to-cluster-dependent-resources-optional), seems this scenario is supported by Service API. So could you take a look this issue? Thanks.
Error message:
```
hdinsight.ClustersClient#Create: Failure sending request: StatusCode=400 -- Original Error: Code="BadRequest" Message="User input validation failed. Errors: The request payload is invalid. Endpoint type 'privatelink' in url wasb://spark-abs-01@ababgstreamspark.privatelink.blob.core.windows.net is neither 'blob' or 'dfs',User input validation failed. Errors: The request payload is invalid. Endpoint type 'privatelink' in url wasb://spark-abs-01@ababgstreamspark.privatelink.blob.core.windows.net is neither 'blob' or 'dfs',User input validation failed. Errors: The request payload is invalid. Endpoint type 'privatelink' in url wasb://spark-abs-01@ababgstreamspark.privatelink.blob.core.windows.net is neither 'blob' or 'dfs'"
```
Contributor guide
Research direction
Start with the error message in the issue and compare the reported request URL with the linked Azure HDInsight private-link documentation. Trace the HDInsight cluster create specification and its endpoint validation; done means the documented private-link storage-container scenario is represented correctly and no longer produces the reported validation error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- api, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100