[Mission] Add mission preview extension (Microsoft.Mission 2026-03-01-preview) - #10149
Conversation
|
Hi @harshitchoudhary, |
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
|
/azp run |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
|
Mission |
689a289 to
46f9283
Compare
…-preview)
Add a new AAZ-generated preview CLI extension `az mission` for Azure Virtual
Enclaves (Microsoft.Mission), covering all 9 resource types at api-version
2026-03-01-preview (pinned spec commit 342124d3):
- communities (+ community-endpoint, dedicated-hub, transit-hub children)
- virtual-enclaves (+ enclave-endpoint, workload children)
- enclave-connections (top-level, under resource group)
- approvals (extension resource: /{resourceUri}/.../approvals/{name})
- POST actions: community check-address-space-availability,
approval notify-initiator, and handle-approval-creation/deletion callbacks
CLI sibling of the shipped Az.Mission PowerShell module (PR #29844).
Generated via aaz-dev (command-model generate-from-swagger + CLI Extension
Generator). Extension marked preview (azext.isPreview). azdev linter, style,
and build all pass; long spec-derived options waived via linter_exclusions.yml.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
The 8 handle-approval-creation/deletion commands (community-endpoint, enclave-connection, virtual-enclave, enclave-endpoint) are RP-internal approvalCallbackRoute callbacks, not customer-facing operations. Unregister them so they no longer appear in `az mission ... --help`. Done regen-safely via the aaz-dev command model (registered=False on the command view + update_module regeneration) rather than hand-editing generated files, so the change survives future aaz-dev codegen. The command classes are retained (reversible); only the @register_command decorator is omitted. azdev linter, style, and build remain green. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
/azp run |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
The azure-cli-extensions CI pipeline (scripts/ci/service_name.py, run as 'azdev style/linter on Modified Extensions') requires every extension's top-level command group to have an entry in src/service_name.json. AAZ codegen does not add this entry. Map 'az mission' -> "Azure Virtual Enclaves" (RP Microsoft.Mission) to satisfy the check. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
/azp run |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
MissionScenario had no test methods, so pytest collected 0 items and azdev returned exit 1, failing the build-test gate on all Python versions (3.10-3.14). Add a no-op offline test_help method (no recordings) matching the durabletask pattern so >=1 test is collected and passes. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
/azp run |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
|
The companion aaz command-model PR is Azure/aaz#1058 (Azure/aaz#1058) — adding per review request. It carries the |
|
Automated sensitive-information remediation ran on this pull request.
If a credential was exposed, rotate or revoke it immediately. Detected values are never copied into this comment. ✅ Keep the redaction · ❌ Dispute the redaction GitHub only supports a fixed reaction set, so 👍 represents ✅ and 👎 represents ❌. The bot-created reactions are only poll choices. Posted by agent-assist (autonomous bug-fix pipeline). |
Related command
az missionInitial AAZ-generated preview CLI extension for the Microsoft.Mission resource provider (Azure Virtual Enclaves / AVE) at API version 2026-03-01-preview. Generated with the aaz-dev-tools swagger (v2) translator from the pinned REST spec commit
342124d3— the same spec the sibling PowerShell module used.What's included
src/mission/, command rootaz mission.community(+ nestedcommunity-endpoint,dedicated-hub,transit-hub,identity)virtual-enclave(+ nestedenclave-endpoint,workload,identity)enclave-connection(top-level, RG-scoped)approval(extension resource:/{resourceUri}/providers/Microsoft.Mission/approvals/{approvalName}, withnotify-initiator)community check-address-space-availabilityaction retained as generated.azext.isPreview: true, version1.0.0b1,azext.minCliCoreVersion: 2.75.0.linter_exclusions.ymlwaives 40option_length_too_longfindings (long generated option names from the spec; accepted repo convention used by ~20 other extensions).Companion work
msazuredev, projectVirtualEnclaves).Open question for reviewers
The 8×
handle-*-approval-creation/handle-*-approval-deletioncommands (oncommunity-endpoint,virtual-enclave,enclave-endpoint,enclave-connection) map to the RP-internalapprovalCallbackRoutePOST operations. They are shipped here for parity with the PowerShell module, but they are not customer-facing. Happy to mark themhidden(or drop them) in the CLI if the CLI team prefers — a regen-safe hide directive is ready and the same cleanup is being coordinated on the sibling PowerShell PR.This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired) —azdev style mission✅ cleanpython scripts/ci/test_index.py -qlocally? (pip install azdevrequired) — ✅OK(9 tests)1.0.0b1(preview/beta)For new extensions:
About Extension Publish
setup.pyversion is1.0.0b1andHISTORY.rstis initialized.src/index.jsonis intentionally not modified — it is updated automatically by the publish pipeline after merge.aaz command models
The companion aaz command-model contribution for this extension is Azure/aaz#1058 (Microsoft.Mission
2026-03-01-preview). That PR adds theCommands/missiontree and theResources/mgmt-planeconfigs these CLI command models are generated from. Sharing it here per review request.