Provenance
- Archive digest
- sha256:6958261576034e6074f328a7b9f9d85841b243541641819c97e8e5b5e603c670
- Report digest
- sha256:d0d9269b985a891b0c2c38673d4bcbfed0ffd0639e2efe10f4cfb90469bde414
- Attestation
- signed (DSSE)
- Signing key
- -_Ea_eEb6AVt8DSP
agentry verify blaktron/azure-environment-setup-guide@0.1.0
Check the key id against the registry's published set at /.well-known/agentry/signing-keys.json. A signature proves who built this release, not that its contents are safe.
Manifest
The manifest as the registry validated and stored it, in canonical JSON.
{
"name": "azure-environment-setup-guide",
"tags": [
"azure",
"cloud",
"setup",
"infrastructure",
"arm",
"report"
],
"guide": {
"task": "e.g. Set up dev and prod for a small web app with a database in West Europe",
"files": "Optional: a requirements document or workload list as text, Markdown or CSV.",
"connect": {
"AZURE_ACCESS_TOKEN": "Optional. Needed only if you want the agent to make changes. It is a short-lived token (about an hour) that carries the rights of whoever created it.\n\n1. Sign in with Azure CLI, preferably as a service principal limited to one resource group: `az ad sp create-for-rbac --name <name> --role Contributor --scopes /subscriptions/<id>/resourceGroups/<rg>`, then `az login --service-principal ...`. Never share the printed secret.\n2. Run `az account get-access-token --resource https://management.azure.com --query accessToken -o tsv`.\n3. Paste the output here.\n\nThe least role that does the job, at the narrowest scope, is best. Without it, the agent works in guided mode."
},
"prepare": [
"Know roughly what you will run in Azure, how many users, and your monthly budget.",
"Have your Azure subscription ID and region preferences, if you already have an account.",
"For direct changes, create a service principal with Contributor on one resource group, or use your own login, and get a token.",
"Leave the token blank to get step-by-step instructions only."
],
"overview": "Walks you through setting up an Azure environment for your needs. It asks for your requirements, proposes a design for your approval, then either makes the changes through Azure Resource Manager (if you give it a short-lived access token) or gives you exact portal and Azure CLI steps. It records everything and ends with a formatted PDF report."
},
"modes": [
"interactive"
],
"license": "MIT",
"publish": {
"include": [
"agent.yaml",
"AGENT.md",
"README.md",
"LICENSE"
]
},
"summary": "Gathers Azure requirements, then sets up the environment directly or gives step-by-step instructions, and writes a PDF report.",
"version": "0.1.0",
"namespace": "blaktron",
"entrypoints": {
"instruction": "AGENT.md"
},
"interactive": {
"opening": "Tell me what you want to run in Azure (an app, VMs, data platform, a team sandbox?), plus your region, budget, who needs access and whether you already have a subscription. I'll ask for the rest, then either make the changes or walk you through them."
},
"capabilities": {
"exec": "none",
"network": {
"egress": [
"management.azure.com",
"learn.microsoft.com"
]
},
"secrets": [
"AZURE_ACCESS_TOKEN"
],
"dataAccess": [
"other"
],
"filesystem": {
"read": "none",
"write": "none"
},
"optionalSecrets": [
"AZURE_ACCESS_TOKEN"
]
},
"schemaVersion": "2"
}