I have set spec.publishId on a container build using v0.13.29 but it doesn't seem to be respected when publishing to a kubernetes provider. Please provide some insight.

Hi @acoustic-laptop-79795 is this perhaps related to this issue: https://github.com/garden-io/garden/issues/5581 ?

It could be. There doesn't seem to be any movement on the issue. Suggestions?

Hi @acoustic-laptop-79795, Sorry for the long waiting time, we have finally got back to looking into this. We opened another GH issue with more context and a reproducible example: https://github.com/garden-io/garden/issues/6050 - I'm currently working on it.

Thanks for the update.

@acoustic-laptop-79795, the issue above was fixed in https://github.com/garden-io/garden/pull/6052. Feel free to try out an edge release. You can get it with

garden self-update edge-bonsai

command. Please let us know if it works as expected. Have a nice weekend! 🙂

Publish Id is now respected when executing "garden publish". Thanks. It does not seem to be respected when executing "garden deploy". Is this the intended behavior?

@acoustic-laptop-79795 yes, that's the expected behaviour. The

publishId

config option is only for

garden publish

command. It's an identifier for public Docker image. For `build`/`deploy` commands you can configure

deploymentRegistry

that is not used by the

garden publish

command.