[Devanshu Singh (thisisdevanshu)]

🤖 PR Validation — ⚠️ Review suggested

Breaking Changes
⚠️ None

⚠️Azure CLI Extensions Breaking Change Test

⚠️planetarycomputer

rule	cmd_name	rule_message	suggest_message
⚠️ 1006 - ParaAdd	planetarycomputer geocatalog create	cmd planetarycomputer geocatalog create added parameter mi_system_assigned
⚠️ 1006 - ParaAdd	planetarycomputer geocatalog create	cmd planetarycomputer geocatalog create added parameter premium_configuration
⚠️ 1006 - ParaAdd	planetarycomputer geocatalog create	cmd planetarycomputer geocatalog create added parameter public_network_access
⚠️ 1010 - ParaPropUpdate	planetarycomputer geocatalog create	cmd planetarycomputer geocatalog create update parameter tier: updated property choices from ['Basic'] to ['Basic', 'Premium']
⚠️ 1006 - ParaAdd	planetarycomputer geocatalog identity assign	cmd planetarycomputer geocatalog identity assign added parameter mi_system_assigned
⚠️ 1006 - ParaAdd	planetarycomputer geocatalog identity remove	cmd planetarycomputer geocatalog identity remove added parameter mi_system_assigned
⚠️ 1011 - SubgroupAdd	planetarycomputer geocatalog private-endpoint-connection	sub group planetarycomputer geocatalog private-endpoint-connection added
⚠️ 1011 - SubgroupAdd	planetarycomputer geocatalog private-link-resource	sub group planetarycomputer geocatalog private-link-resource added
⚠️ 1006 - ParaAdd	planetarycomputer geocatalog update	cmd planetarycomputer geocatalog update added parameter public_network_access

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

az planetarycomputer geocatalog

Existing GeoCatalog and identity commands, plus:

• az planetarycomputer geocatalog private-endpoint-connection create/delete/list/show/update/wait
• az planetarycomputer geocatalog private-link-resource list

Summary

Update the existing Planetary Computer extension to Microsoft.Orbital API version 2026-10-01 and extension version 1.0.0b2.

• Preserve the existing public command names and option aliases, including --scope.
• Add private endpoint connection and private link resource commands.
• Add Premium tier configuration, public network access, and system-assigned identity options.
• Expose the API's read-only lifecycle fields; no start/stop commands are introduced.
• Add an offline smoke test that invokes the real CLI with mocked HTTP responses.

Companion public TypeSpec and Swagger draft: Azure/azure-rest-api-specs#47502

The corresponding AAZ command model changes are prepared locally; the companion AAZ PR is still pending.

Validation and draft follow-up

Completed locally:

• Offline smoke test passes: API version and Microsoft.Orbital routes, Premium request serialization, identity/network settings, the 5 PB capacity boundary, stopped-state output, and private link listing.
• All 15 deliberate in-memory mutations are detected by the smoke test; generated source files were not modified by mutation verification.
• azdev style planetarycomputer passes pylint and flake8.
• python scripts/ci/test_index.py -q passes: 9 tests, 2 skipped.
• git diff --check and the normal pre-commit secret scan pass.
• AAZ command model verification passed during generation.

Not ready to merge:

• CLI linter: the normal push hook reports option_length_too_long for --private-link-service-connection-state on private endpoint connection create and update. Add a short option alias through the AAZ workspace and regenerate.
• Playback recordings: existing recordings target 2026-04-15; the previous playback run fails against requests using 2026-10-01. Refresh recordings against an authorized live environment. The current push hook stopped at the CLI linter, so it did not rerun playback.
• Publish/link the companion AAZ model PR.
• CI and live-service validation remain pending. The offline smoke test is not a substitute for live recordings, and existing recordings have not been edited to simulate new service evidence.

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install azdev required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

Not applicable: this updates an existing extension.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Aditya Pujara (a0x1ab)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 2 pipeline(s).