Skip to content

[azure-planetarycomputer] Regenerate SDK from latest TypeSpec#45219

Closed
chahibi wants to merge 173 commits intoAzure:mainfrom
chahibi:mpcpro-regen
Closed

[azure-planetarycomputer] Regenerate SDK from latest TypeSpec#45219
chahibi wants to merge 173 commits intoAzure:mainfrom
chahibi:mpcpro-regen

Conversation

@chahibi
Copy link
Member

@chahibi chahibi commented Feb 17, 2026

Description

Regenerates the azure-planetarycomputer SDK from the latest TypeSpec at Azure/azure-rest-api-specs@1d0c549 (specification/orbital/Microsoft.PlanetaryComputer).

Changes included:

  • Regenerated client code via npx tsp-client update
  • Applied required pylint suppressions on generated code (too-many-lines, too-many-locals, import-error, unused-import, no-value-for-parameter)
  • Fixed Sphinx docstring formatting in DataOperations.get_interval_legend (missing newline after JSON code block, bullet continuation indentation)
  • Updated samples to reflect renamed API (see breaking changes below)
  • Added a package-level CONTRIBUTING.md documenting the post-generation manual fix workflow

Local validation: Black, Pylint (10.00/10), MyPy, Pyright, and Sphinx all pass.

Breaking Changes

The updated TypeSpec introduces the following breaking changes. Users upgrading from the previous preview will need to update their code accordingly.

Change Before After
Method rename StacOperations.list_collections() StacOperations.get_collections()
Return type change StacOperations.list_queryables() returned dict[str, Any] Returns QueryableDefinitionsResponse
Return type change StacOperations.get_collection_queryables() returned dict[str, Any] Returns QueryableDefinitionsResponse

New models added (non-breaking)

AssetStatisticsResponse, BandStatisticsMap, ClassMapLegendResponse, QueryableDefinitionsResponse, TilerAssetGeoJson, TilerInfoMapResponse

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant