Azure / Azure/apiops

[BUG] Publisher gets 400 from Azure

Offen
#719 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
C#
Sterne
448
Forks
247
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

### Release version

v6.0.1.3

### Describe the bug

I already have configuration of APIM in my GitHub repo collected by v5 of ApiOps. I extract everything successfully using v6.0.1.3. It created a few not essential changes related to a version (e.g. changed order of parameters in json). So almost the same configuration was published by v5 of ApiOps successfully. When I run publisher v6 it can't complete PUT operation. As you can see in log below publisher excludes "displayName" property from "Content". I tried to run the same API request manually and it actually does not work. It works only if we have "displayName" property in Content of request.

This is description of named value:
{
"properties": {
"displayName": "TestNamedValue",
"secret": false,
"tags": [],
"value": "some_value"
}
}

This is log:
Starting request
Method: PUT
Uri: https://management.azure.com/subscriptions/***/resourceGroups/***/providers/Microsoft.ApiManagement/service/***/namedValues/TestNamedValue?api-version=2023-09-01-preview
Content: {"properties":{"secret":false,"tags":[],"value":"some_value"}}
trce: HttpPipeline[0]
Received response
Method: PUT
Uri: https://management.azure.com/subscriptions/***/resourceGroups/***/providers/Microsoft.ApiManagement/service/***/namedValues/TestNamedValue?api-version=2023-09-01-preview
Status code: 400
Duration (hh:mm:ss): 00:00:00.5015046
Content: {"error":{"code":"ValidationError","message":"One or more fields contain incorrect values:","details":[{"code":"ValidationError","target":"name","message":"NamedValue (display name) should be between 1 and 256 characters long."}]}}
crit: publisher[0]
Application failed.
System.Net.Http.HttpRequestException: HTTP request to URI https://management.azure.com/subscriptions/***/resourceGroups/***/providers/Microsoft.ApiManagement/service/***/namedValues/TestNamedValue?api-version=2023-09-01-preview failed with status code 400. Content is '{"error":{"code":"ValidationError","message":"One or more fields contain incorrect values:","details":[{"code":"ValidationError","target":"name","message":"NamedValue (display name) should be between 1 and 256 characters long."}]}}'.

### Expected behavior

Expected successful publishing

### Actual behavior

'{"error":{"code":"ValidationError","message":"One or more fields contain incorrect values:","details":[{"code":"ValidationError","target":"name","message":"NamedValue (display name) should be between 1 and 256 characters long."}]}}'.

### Reproduction Steps

Extract configuration of Named Values.
Publish extracted configuration.

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Beginne damit, den named-value flow nachzustellen: Extrahiere die Konfiguration und veröffentliche anschließend die extrahierte Konfiguration mit v6. Vergleiche den Inhalt der PUT-Anfrage mit der im Issue funktionierenden manuellen Anfrage und betrachte das Issue als erledigt, wenn Azure die Anfrage akzeptiert und die Veröffentlichung erfolgreich abgeschlossen wird.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
azure, csharp
Bereich
api, cloud
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.