Open davidfowl opened 1 month ago
Locally we don't run the .NET project inside a container, so volumes and mounts don't immediately make sense - but it totally makes sense that you might want to do this when you deploy.
We could extend the API surface to allow applying the annotations to the ProjectResource
and extend the manifest so we can write these fields. AZD would need to be extended to support it as well.
Locally we don't run the .NET project inside a container
Wait! I thought the .NET projects are running on containers. It got an extension for running with replicas, so I assumed it is containerized.
With the understanding that .NET projects are running on container, I was thinking of making some sort of contribution through an implementation with Docker volumes at first. Then, extend it later for Podman and Kubernetes. But it looks like there are things needed to be done first.
And an extension for this, I think it would be good to have an implementation of mounting volumes from SMB(with authentication) like Azure File Share. Or probably some sort of abstract for PersistentVolume and PersistentVolumeClaims.
They run as container when they are deployed, not locally.
Discussed in https://github.com/dotnet/aspire/discussions/4336