Customizing generated container-app bicep from a TypeScript AppHost #19009
Unanswered
Anton Sokolovskyi (antsok)
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I need to set ACA properties that Aspire's generated bicep hardcodes — specifically activeRevisionsMode (emitted as 'Single'), also maxReplicas / terminationGracePeriodSeconds.
Using the TypeScript AppHost with CLI 13.4.6. What I've hit:
publishAsAzureContainerApp((infra, app) => ...) runs, but the app handle only projects configureScale / configureCustomDomain; setting app.configuration.activeRevisionsMode is a silent no-op.
configureInfrastructure exists in the TS bindings, but the AzureResourceInfrastructure object has no getProvisionableResources() (the docs at aspire.dev/integrations/cloud/azure/customize-resources say to use it — it's absent from the generated bindings). I believe this is Polyglot ConfigureInfrastructure for Azure resources #14828.
Eventing works (subscribeBeforePublish/subscribeAfterPublish both fire, even under aspire deploy), but event.model() returns inert IResource handles, and the synthesized container-app resource never appears in the model.
Last resort: an subscribeAfterPublish callback that patches the emitted .bicep on disk. This works for aspire publish, but under aspire deploy the --output-path directory is never even created — deploy apparently provisions the templates in memory, so there's nothing to patch.
Questions:
(1) Is there any supported way on 13.4.6 to override a generated container-app property from a TS AppHost?
(2) Is aspire deploy ever going to read bicep from the artifact path, or is in-memory provisioning by design?
(3) Is #14828 (polyglot ConfigureInfrastructure, milestone 13.5) the right issue to watch, or is there something sooner?
All reactions