The feature to list subset of revisions using the range request header is defined in the REST API docs but doesn't exist in the typespec spec

[ahsonkhan]

REST API doc:
https://learn.microsoft.com/en-us/azure/azure-app-configuration/rest-api-revisions?pivots=v23-11#list-subset-of-revisions

The Typespec spec doesn't mention Range:
https://github.com/Azure/azure-rest-api-specs/blob/b6bead0df961af706e984e2b9807c8a099ece61b/specification/appconfiguration/AppConfiguration/routes.tsp#L812

If this capability is necessary, we'd need to get the service team to update the typespec to include this feature.
Until then, we could either hand-implement this, or exclude it from the public surface area, until requested by customers.

Since, the other language SDKs don't have this capability either, we'd follow suite. So, this will be in the backlog for C++ for now.

• GoLang
• .NET

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @ahsonkhan @antkmsft @gearama @LarryOsterman @RickWinter.

[ahsonkhan]

From the service team:

It looks like an oversight. Revisions endpoint is the only one that supports Range header.

Based on feedback from Typespec and Codegen folks, @avanigupta, this is something we'd want fixed in the service spec.

The goal is for the service's TypeSpec spec to be a true (and a more complete) representation of the public/documented/supported service behavior.

P.S. In this case, since other languages have a convenience layer on top, each language SDK can choose how they would like to wire things internally and how/when to expose it to customers.