Regarding containerApp.tmpl.yaml
Describe the issue or suggestion
Team, Greeting. The documentation is pretty great. I have some suggestions. URL: https://github.com/dotnet/docs-aspire/blob/main/docs/deployment/azure/aca-deployment-azd-in-depth.md
These are the artifacts it will generate mentioned.
- infra/main.bicep: Represents the main entry point for the deployment.
- infra/main.parameters.json: Used as the parameters for main Bicep (maps to environment variables defined in .azure folder).
- infra/resoures.bicep: Defines the Azure resources required to support the .NET Aspire project model.
- AspireSample.Web/manifests/containerApp.tmpl.yaml: The container app definition for webfrontend.
- AspireSample.ApiService/manifests/containerApp.tmpl.yaml: The container app definition for apiservice.
A little bit further you guys mentioned
The definition of the container apps from the .NET service projects is contained within the containerApp/tmpl.yaml files in the manifests directory in each project respectively. Here is an example from the webfrontend project:
But when I execute the command it has created these artifacts.
I am unable to understand. Could you please fix this? Many thanks.
Regards, Swamy
We have to update this now that we changed everything 😄
cc @vhvb1989 @mitchdenny
Hello,
I am facing the similar issue and i dont even see any manifest file generated for the same.
cc @vhvb1989 @mitchdenny
I am facing the similar issue and i dont even see any manifest file generated for the same.
Can you clarify what you mean?
@vishipayyallore Hi Swamy, I wanted to ask...is this still an issue? I'm inclined to close this as I think it's been addressed, please let me know.
@vishipayyallore Hi Swamy, I wanted to ask...is this still an issue? I'm inclined to close this as I think it's been addressed, please let me know.
Hi @IEvangelist David, Please close the ticket.