Azure / Azure/azure-rest-api-specs

Microsoft.Web/connections@2016-06-01 - properties.parameterValues should allow more types than string

Open
#21,096 2 comments 1 reaction 0 assignees View on GitHub
Service Attention Web Apps
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
2d 22h
Merged PRs (30d)
444

Description

The swagger definition is inaccurate, the parameterValues allow other types: boolean, integer, object, for example:

```hcl
parameter_values = {
"gateway": {
"id": "/subscriptions/.../resourceGroups/.../providers/Microsoft.Web/connectionGateways/...",
}
"client": ...some int...,
"authType": "basic",
"logonType": "ApplicationServer",
"appServerHost": "...",
"appServerService": "...",
"systemNumber": "...",
"safeTyping": false,
"useSnc": false,
"sncSso": "On",
"sncQop": "Authentication"
}
```

link: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/web/resource-manager/Microsoft.Web/stable/2016-06-01/logicAppsManagementClient.json#L1880

Contributor guide

Open the contributing guide

Research direction

Start at specification/web/resource-manager/Microsoft.Web/stable/2016-06-01/logicAppsManagementClient.json around line 1880 and inspect the parameterValues schema. Compare its current type with the boolean, integer, and object examples in the issue; done means the specification accepts those value types as well as strings.

Written by the indexing model from the issue text.

Assessment

Tech stack
openapi
Domain
api
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.