Azure Container Instances (ACI)
Build and deploy Fabric Harness containers to Azure Container Instances with managed identity.
The Azure Container Instances (ACI) target builds the image in Azure Container Registry and creates or replaces a public ACI container group using managed identity for image pull.
Generated artifact
AciBuildPluginintegrates ACI with the build pipeline.aciReadme()generates resource and deployment instructions.AciDriverexposes the ACI deploy orchestration contract.
Build invocation
fh build --target aciThis emits README.aci.md with the exact image, resource, and ARM deployment steps for the artifact.
Deploy
The ACI target is registered in the build system and deploy registry. Use it like any other target:
export AZURE_ACR_NAME=fabricregistry
export AZURE_RESOURCE_GROUP=agents-rg
export AZURE_CONTAINER_NAME=support-agent
export AZURE_LOCATION=westus3
fh deploy --target aciOptional variables:
| Variable | Default |
|---|---|
AZURE_ACR_REPOSITORY | fabric-harness |
AZURE_IMAGE_TAG | latest |
AZURE_ACI_IDENTITY | [system] |
AZURE_ACI_CPU | 1 |
AZURE_ACI_MEMORY_GB | 1.5 |
AZURE_ACI_DNS_NAME_LABEL | unset |
PORT | 3000 |
Grant the selected managed identity AcrPull on the registry. fh deploy --preview --target aci
prints the commands without changing Azure resources. Runtime secrets remain external to the build;
configure them through your deployment environment or secret delivery path.