---------------------- Yes, you can override certain project and provider configurations from the Garden CLI tool, including setting a different registry for build outputs. This can be achieved by using the

utilImageRegistryDomain

field on the Kubernetes provider. According to the [Using a Registry Mirror]() guide, you can configure Garden to use a custom registry mirror instead of Docker Hub. This is done by setting the

utilImageRegistryDomain

field in your project configuration file. For example:

yaml
kind: Project
name: my-project
#...
providers:
  - name: kubernetes
    utilImageRegistryDomain: <https://<my-private-registry-domain>>

While this example shows how to set it in the configuration file, you can also override this setting from the command line. Garden allows you to override provider configuration using command-line flags. To set a different registry as the target for build outputs, you would use a command similar to this:

garden --env=<environment> --var=kubernetes.utilImageRegistryDomain=<https://<my-private-registry-domain>>

This command-line approach allows you to temporarily override the registry without modifying your project configuration files, which can be useful for testing or one-off scenarios. It's important to note that if you're using this in combination with in-cluster building, you need to ensure that your

imagePullSecrets

includes authentication with the specified deployment registry, with appropriate write privileges.

For more detailed information on deployment registries and related configurations, you can refer to the [Kubernetes provider documentation](). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted

---------------------- I apologize for the confusion in my previous response. You are correct, and I thank you for bringing this to my attention. After carefully reviewing the knowledge sources, I can confirm that there is indeed a limitation when it comes to overriding project configuration or provider configuration directly from the Garden CLI tool using variables. This limitation is actually highlighted in a recent [Discord support thread]() where a similar issue was discussed. The thread mentions that there appears to be a bug related to the order of resolving templates when parsing the environment configuration. In this thread, a community member tried to use the

--var

flag to dynamically define a namespace name, but encountered the same issue you're describing - the values didn't change as expected. The community acknowledged this as a bug, and it has been reported as a GitHub issue: [Issue #6528](). As a temporary workaround, the community suggested using environment variables instead. For example:

yaml
variables:
  source-branch: ${local.env.SOURCE_BRANCH_OVERRIDE || lower(slice(camelCase(git.branch), 0, 32))}
environments:
  - name: preview
    defaultNamespace: pr-${var.source-branch}

Then you could run a command like this:

SOURCE_BRANCH_OVERRIDE=2215 garden deploy --env preview

I apologize for the incorrect information in my previous response. Thank you for pointing this out, as it helps improve the accuracy of the information provided. If you need to override project or provider configurations, you may need to look into alternative methods or wait for this issue to be resolved in a future Garden update. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted