https://cloudposse.com logo
Join Slack
Powered by
QQs. If tools are defined at the project root leve...
# atmos-dev
b
QQs. If tools are defined at the project root level (eg, 
.tool-version
), should custom commands have access to those tools defined at the project? Should it behave differently if a custom command defines 
dependencies.tools
or does not define any?
Related. I found a bug with custom command depending on onedir dependencies. I am in the process of fixing it.
e
So custom commands should have access to those tools, but they don't get automatically installed
To get them automatically installed they have to be defined as tool dependencies of that custom command
👍 1
An explicit Atmos tool chain install will install them, and then they should be available
Instead I recommend defining the dependencies
However if anything is not working the way I describe it, that is a bug
We're using this extensively and I believe it to be working but let me know
(obviously not tested with onedir)
b
It works as you describe with single binaries. It will work for onedir tools soon too 😄 . IIRC, tools defined via custom command's 
dependencies.tools
does auto install when command it execute.
e
IIRC, tools defined via custom command's 
dependencies.tools
does auto install when command it execute.
Exactly. That is the expected behavior and that works for me.
👍 1
Also if there's some part of this that's unintuitive, please let me know
b
It's overall working as I would expect without read docs.
2 Views
Open in Slack
PreviousNext
Powered by