vscode-azurecontainerapps
AGENTS.md42 starsChanged 4 days agoMITView on GitHub
Use .github/copilot-instructions.md for implementation, verification, and review rules. Subsystem contracts live in .github/instructions. package.json contributions and package.nls.json labels -> src/commands/registerCommands.ts -> command and wizard steps -> Azure Tools helpers or src/utils/azureClients.ts -> ARM operation or local revision draft -> tree state, activity/output, and tests.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repositoryOne other file it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Use .github/copilot-instructions.md for implementation, verification, and review rules.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Azure Container Apps extension architecture
Use .github/copilot-instructions.md for implementation, verification, and review rules. Subsystem contracts live in .github/instructions.
Follow a user action
package.json contributions and package.nls.json labels ->
src/commands/registerCommands.ts -> command and wizard steps ->
Azure Tools helpers or src/utils/azureClients.ts ->
ARM operation or local revision draft -> tree state, activity/output, and tests.
Code ownership map
| Area | Start here | Boundary |
| Activation | src/extension.ts, src/extensionVariables.ts, src/commands/api/createContainerAppsApiProvider.ts | Registers shared extension variables, commands, revision-draft filesystem, and the Azure Resources API handshake. The tracked loader main.js measures bundle load time; do not modify it. |
| Resource explorer | src/tree/ContainerAppsBranchDataProvider.ts, src/tree/ManagedEnvironmentItem.ts, src/tree/ContainerAppItem.ts | The rich hierarchy is environment -> app -> template children or revisions, plus configuration and logs. ext.state wraps items with operation state. |
| Standalone app group | src/tree/ContainerAppResourceItem.ts, src/commands/revealInEnvironment.ts | Flat app nodes use a distinct #flat tree ID and reveal the rich environment hierarchy; their tree IDs are not ARM resource IDs. |
| Azure clients and resource picking | src/utils/azureClients.ts, src/utils/pickItem/, src/utils/getResourceUtils.ts | Shared Azure Tools factories and subscription contexts own authentication; local helpers select the appropriate app, environment, revision, or container. |
| Create resources | src/commands/createContainerApp/, src/commands/createManagedEnvironment/, src/commands/EXECUTE_PRIORITY.md | List steps inject create/update subwizards. Follow Express compatibility instructions for mode-specific defaults and optional logging. |
| Workspace deployment | src/commands/deployWorkspaceProject/ | Resolves workspace/tree configuration, migrates saved settings, coordinates creation/build/deploy, and returns deployment results. |
| Images and registry access | src/commands/deployContainerApp/, src/commands/deployImage/, src/commands/image/, src/commands/registryCredentials/ | Existing images versus remote ACR builds; managed identity/AcrPull versus Docker login; startup verification is separate from build and ARM completion. |
| Revisions and configuration | src/commands/revision/, src/commands/revisionDraft/, src/utils/revisionDraftUtils.ts, src/commands/updateContainerApp.ts | Revision templates are edited through an in-memory filesystem; app-level configuration and secrets have different mutation paths. |
| Configuration UI | src/tree/configurations/, src/tree/containers/, src/tree/scaling/, src/tree/revisionManagement/ | Ingress/secrets are app configuration; containers/environment variables/scaling participate in revision templates and draft editability rules. |
| Logs and portal actions | src/commands/logStream/, src/tree/LogsGroupItem.ts, src/commands/openConsoleInPortal.ts | Revision/replica/container selection, authenticated streaming, and portal links; the console action opens the portal, not an extension-owned exec/debug tunnel. |
| Confirmation UI and Copilot | src/webviews/, src/commands/copilot/ | React/Fluent UI views and extension-side controllers coordinate wizard confirmation, edit/back/cancel state, and Copilot input. |
| Workspace helpers | src/utils/settingUtils.ts, src/utils/workspaceUtils.ts, src/node/fs-extra.ts, src/browser/fs-extra.ts | Resource-scoped configuration, multi-root selection, and separate filesystem adapters; do not assume all Node operations work in a browser host. |
| Public API | src/commands/api/vscode-azurecontainerapps.api.d.ts, src/commands/api/CHANGELOG.md | Versioned deployImage and deployWorkspaceProject contracts, plus compatibility command registration. Test-only exports live in src/testApi.ts. |
| Tests and engineering | test/, package.json, esbuild.mjs, .vscode-test.mjs, .github/workflows/main.yml, .config/ | VS Code-hosted tests, gated live-Azure scenarios, and shared Azure Tools build/pipeline configuration. |
External ownership
@microsoft/vscode-azext-utilsowns action/error handling, wizards, activities, tree state, and test UI helpers.@microsoft/vscode-azext-azureutilsowns common Azure resource UI, subscription client construction, provider verification, and related authentication helpers.@microsoft/vscode-azext-githubsupplies shared GitHub integration helpers; repository connection orchestration lives insrc/commands/gitHub/.- The Azure Resources extension hosts the resource explorer and subscription
picker. Its API handshake is required before using
ext.rgApiV2. - Azure SDK packages own service models and operations, not the extension's draft, confirmation, workspace-settings, or tree-refresh contracts.
@microsoft/vscode-azext-engandmicrosoft/vscode-azuretoolsown shared engineering configuration and CI templates. Review ownership is recorded in .github/CODEOWNERS.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.