Azure / Azure/terraform

CustomVision Kind : both

Open
#323 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
HCL
Stars
925
Forks
930
Avg merge
4d 15h
Merged PRs (30d)
5

Description

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Where would you like this feature added?

Examples (Quickstart, Samples, etc.)

### Is this feature ask due to a problem that you are encountering?

When using terraform to create CustomVision resource, only "CustomVision.Prediction" or "CustomVision.Training" is supported.

```
resource "azurerm_cognitive_account" "cognitive_service" {
name = "CognitiveService-${random_string.azurerm_cognitive_account_name.result}"
location = azurerm_resource_group.rg.location
resource_group_name = azurerm_resource_group.rg.name
sku_name = var.sku
kind = "CustomVision.Prediction"
}
```

However the Azure Portal also supports a resource type both.
![image](https://github.com/Azure/terraform/assets/111774741/c0d0b760-4158-41ba-90cc-06fdd78c3fad)

How can this be supported with Terraform?

### Describe potential solutions.

Adding a new parameter in kind field to support Custom Vision resource type both.

### Anything else?

_No response_

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the Terraform resource implementation and validation for azurerm_cognitive_account's kind field, then check how CustomVision.Prediction and CustomVision.Training are represented. Done means the kind value for a combined Custom Vision resource is accepted and can be used to create the resource consistently with the Azure Portal.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, terraform
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.