Azure / Azure/oav

oav generate-examples not adding LRO headers in samples

Open
#1,061 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
104
Forks
62
Avg merge
2d 12h
Merged PRs (30d)
5

Description

Hi team,

For a TSP Interface of ArmResourceActionAsync like so (LRO headers reqd = **AzureAsync**, **Location**, **Retry-After**):


![Image](https://github.com/user-attachments/assets/a752516a-58e1-4f4b-83a5-0a85939b765c)

TSP compile yields an openAPI.json like so (all 3 headers present):

![Image](https://github.com/user-attachments/assets/10a60799-1477-4ba9-b831-0d534dccc140)

however, the json sample created for this async action, the sample captures only **Location** (Azureasync and Rety-after missing):

![Image](https://github.com/user-attachments/assets/3d9f76c7-a925-489a-ab4c-3f68e207183b)


Should the sample also not capture other headers ?

Contributor guide

Open the contributing guide

Research direction

Start with the oav generate-examples command and compare its handling of the openAPI.json response headers with the generated JSON sample. Verify whether AzureAsync, Location, and Retry-After are preserved for ArmResourceActionAsync; done means the sample captures all three headers.

Written by the indexing model from the issue text.

Assessment

Tech stack
openapi, typescript
Domain
api
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.