How to suppress the inclination of the daml tool to install itself?

I use the daml sdk in a hermetic build under bazel. The daml sdk tarball is an input to the build (an external workspace in bazel lingo) and the build accesses the tools from the sdk as needed (through build targets defined for the external workspace and a toolchain configuration).

Unfortunately, the daml tool does not tolerate well to be used directly from its location in the sdk. If I do that, it sometimes (but apparently not always) tries to download an sdk tarball and install it somewhere else. This seems to happen for daml sandbox, but not for daml build.

Is there a way to suppress this unfortunate behavior for all subcommands?

You can set auto-install: false in your global daml.yaml. However, it shouldn’t randomly install things. It only installs something if the required version is not already installed so likely this will just turn it into an error but hopefully it gets easier to debug why it is trying to install things.

What is my global daml.yaml file? I was only aware of the project one. Where would the global one be found?

Thanks!
mesch.

Ah, just saw it was linked from the response.

Thanks again!
mesch.