Azure / Azure/typespec-azure

[resource-manager]: Make default LRO Options for RPaaS services more explicit

Open
#5,307 0 comments 0 reactions 0 assignees View on GitHub
feature lib:azure-resource-manager triaged:core
Dominant language
TypeScript
Stars
27
Forks
90
Avg merge
1d 22h
Merged PRs (30d)
156

Description

Add documentation, samples, and perhaps operation aliases for preferred LRO Options for RPaaS operations.

Currently, the default templates are using some older patterns (like location header), and we should
(1) Have clear documentation on which templates to use
(2) Have an RPaaS LRO sample that demonstrates appropriate usage
(3) Consider template aliases for RPaaS LROs that use RPaaS recommended options

Contributor guide

Open the contributing guide

Research direction

Start by locating the default LRO templates and any existing RPaaS samples in the repository, then compare their options with the recommended RPaaS patterns described in the issue. Done means the preferred templates are documented, an RPaaS LRO sample demonstrates the usage, and any agreed operation aliases are included; the issue leaves the exact files and alias scope to determine.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.