Azure / Azure/typespec-azure

Investigate Removing 200 response in Async Action templates

Open
#3,254 2 comments 0 reactions 1 assignee Claimed by @markcowl View on GitHub
design:accepted epic lib:azure-resource-manager
Dominant language
TypeScript
Stars
27
Forks
90
Avg merge
1d 22h
Merged PRs (30d)
156

Description

TypeSpec emitters will not use the 200 response, but the result form getLroMetadata to determine the final response value. Need to ensure that other users of OpenApi specs do not requre the 200 response, but can use `x-ms-long-running-operation-options.final-state-schema` to determine the logical result of the operation.

- [x] Check that all Autorest management SDK emitters can use final-state-schema
- [x] Check that cli emitters can use final-state-schema
- [x] Check that other consumers of the spec either don't need this information, or can use final-state-schema

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.