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
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
Is there a way to suppress this unfortunate behavior for all subcommands?