Azure / Azure/azure-rest-api-specs

[BUG] `None ` value of `preferredAppGroupType` property is not valid for creating a Desktop Virtualization Host Pool

Open
#29,220 0 comments 1 reaction 0 assignees View on GitHub
bug customer-reported Desktop Virtualization Mgmt question Service Attention
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
2d 22h
Merged PRs (30d)
444

Description

### API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/65da315d93751e6e06ffd42f44a77f5b1dac27bc/specification/desktopvirtualization/resource-manager/Microsoft.DesktopVirtualization/stable/2024-04-03/desktopvirtualization.json#L4960C11-L4960C13

### API Spec version

2024-04-03

### Describe the bug

Possible values for the property [preferredAppGroupType](https://github.com/Azure/azure-rest-api-specs/blob/65da315d93751e6e06ffd42f44a77f5b1dac27bc/specification/desktopvirtualization/resource-manager/Microsoft.DesktopVirtualization/stable/2024-04-03/desktopvirtualization.json#L4785C10-L4785C31) include `None`, but `None` is not allowed when creating a Desktop Virtualization Host Pool. See below for details.
![image](https://github.com/Azure/azure-rest-api-specs/assets/39109137/4637363b-d8ab-4bed-8a16-1a73513abc77)

### Expected behavior

Following the API spec `None` should be allowed.

### Actual behavior

The following error occurs:
```
"error": {
"code": "400",
"message": "ActivityId: 5abae8b1-e723-46d4-b505-038af70859a8 Error: The PreferredAppGroupType value is incorrect. Please provide a valid type: Desktop or RailApplications."
}
```

### Reproduction Steps

Create a Desktop Virtualization Host Pool and set the `preferredAppGroupType` to "None".

### Environment

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the linked desktopvirtualization.json API specification at the preferredAppGroupType definition and review the 2024-04-03 version. Reproduce host pool creation with preferredAppGroupType set to "None", then determine whether the specification or service behavior needs correction; done means the documented allowed values match the observed API behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, openapi
Domain
api, cloud
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.