Additional customization for docker-compose publisher for service source

[MarioGK]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

It would be great if we could configure the docker service source if it is an "image" or a "build".

Describe the solution you'd like

Maybe in the AppHost we could have an overload for the WithComputeEnvironment to have an options so we could customize the current resource in that environment.
Example:

.WithComputeEnvironment(compose, options =>
                    {
                        options.ImageName = "test";
                        // Prefer Build.XXX if not null, otherwise use the options.ImageName otherwise use the current name.
                        options.Build.Context = ".";
                        options.Build.Dockerfile = "Dockerfile";
                        // or
                        options.BuildContext = ".";
                        options.BuildDockerfile = "Dockerfile";
                    })

So instead of:

  webapp:
    image: "${WEBAPP_IMAGE}"

We would have:

  webapp:
    build:
      context: .
      dockerfile: ./WebApp//Dockerfile

In the final docker-compose.yaml, this would facilitate having deployment per PR for example or just do a quick and dirty test on another environment.

This would enable easy deploy in Dokploy, Coolify and similar easy self hosted services.

Additional context

No response

[MarioGK]

Sorry for creating this issue, it seems this already has an to customize the docker service, by doing the following:

.WithComputeEnvironment(compose)
               .PublishAsDockerComposeService((resource, service) =>
                {
                    service.Image = null;
                    service.Build = new Build
                    {
                        Context = ".",
                        Dockerfile = "./ProjectName/Dockerfile"
                    };
                })

Added an example if someone ever finds this issue.
Sorry again for the issue will close it.