Azure / Azure/oav

Model validation rule "LRO_RESPONSE_HEADER" does not check for the Operation-Location header

Open
#785 1 comment 0 reactions 1 assignee Claimed by @raych1 View on GitHub
enhancement
Dominant language
TypeScript
Stars
104
Forks
62
Avg merge
2d 12h
Merged PRs (30d)
5

Description

I have authored a long-running operation that is getting flagged even though I have specified that it returns the `Operation-Location` header.

The rule that is being triggered has the following description:
> Long running operation must return location header or azure-AsyncOperation header in response when this operation is annotated with x-ms-long-running-operation:true.

However, according to the latest [Azure REST API Guidelines](https://github.com/microsoft/api-guidelines/blob/vNext/azure/Guidelines.md#long-running-operations-with-status-monitor)
> ✅ DO return the status monitor URL in the Operation-Location response header.

In other words, validation should check and accept either one of the following headers: `Location`, `Azure-AsyncOperation`, or `Operation-Location`.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.