Skip to content

fix: deploy application resources to the application resource group - #155

Merged
Paulo Lacerda (placerda) merged 3 commits into
developfrom
feature/app-resource-group
Oct 27, 2026
Merged

Paulo Lacerda (placerda) merged 3 commits into
developfrom
feature/app-resource-group

Conversation

@placerda

Copy link
Copy Markdown
Collaborator

Summary

  • Use AZURE_APP_RESOURCE_GROUP for application registry, identity and Container App operations in both deployment hooks.
  • Fall back to the legacy root setting only when the application key is successfully read as absent or empty; preserve authorization and transport failures.
  • Keep existing single-group and application-root environments compatible.

Coordination

Supports the Foundry-root interface being prepared in Azure/agent-landing-zone. Component release tags and umbrella pins are coordinated separately.

Prefer AZURE_APP_RESOURCE_GROUP with a missing-key-only legacy fallback, preserving explicit lookup failures in both deployment hooks.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Run deployment-script contracts in the checkout suite, not in wheel and container runtime suites where host deployment scripts are intentionally absent. Preserve the full installed runtime coverage and skip-free acceptance requirements.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Restore the protected container helper unchanged and discover deployment contracts in a dedicated source-only package.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@placerda
Paulo Lacerda (placerda) merged commit beb27b3 into develop Oct 27, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant