Azure / Azure/azure-rest-api-specs

[BUG]The specified 'SecondaryType' value was not returned

Open
#35,500 0 comments 0 reactions 0 assignees View on GitHub
bug
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/e279afeeeee8feb7dae9d24e66095d2ce81791c6/specification/sql/resource-manager/Microsoft.Sql/stable/2023-08-01/FailoverGroups.json#L74

### API Spec version

2023-08-01

### Describe the bug

The [FailoverGroups_Get](https://github.com/Azure/azure-rest-api-specs/blob/e279afeeeee8feb7dae9d24e66095d2ce81791c6/specification/sql/resource-manager/Microsoft.Sql/stable/2023-08-01/FailoverGroups.json#L74) does not return the
[secondaryType ](https://github.com/Azure/azure-rest-api-specs/blob/e279afeeeee8feb7dae9d24e66095d2ce81791c6/specification/sql/resource-manager/Microsoft.Sql/stable/2023-08-01/FailoverGroups.json#L621)value, even when it is explicitly specified during the creation of the failover group.

### Expected behavior

The [FailoverGroups_Get](https://github.com/Azure/azure-rest-api-specs/blob/e279afeeeee8feb7dae9d24e66095d2ce81791c6/specification/sql/resource-manager/Microsoft.Sql/stable/2023-08-01/FailoverGroups.json#L74) should return specified secondaryType value.

### Actual behavior

No `secondaryType` value was returned.

### Reproduction Steps

Step1: Create a failover group specifying the `secondaryType`.
Step2: Call [FailoverGroups_Get](https://github.com/Azure/azure-rest-api-specs/blob/e279afeeeee8feb7dae9d24e66095d2ce81791c6/specification/sql/resource-manager/Microsoft.Sql/stable/2023-08-01/FailoverGroups.json#L74) and check if `secondaryType` is returned.

### Environment

_No response_

Contributor guide

Open the contributing guide

Research direction

Read specification/sql/resource-manager/Microsoft.Sql/stable/2023-08-01/FailoverGroups.json, especially the FailoverGroups_Get operation near line 74 and secondaryType near line 621. Reproduce the create-and-get sequence described in the issue and compare the response with the specification; done means the specified secondaryType is returned or the discrepancy is resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
openapi
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.