Query around new cache policy

[scarlet yarrow]

We are planning to upgrade engine from 0.13.0. -> 0.14.0

and I see this in release notes - https://github.com/dagger/dagger/pull/8725

Our existing engine.toml has this configuration

[[worker.oci.gcpolicy]]
  keepBytes = "2400000MB"
  keepDuration = "0"
[[worker.oci.gcpolicy]]
  keepDuration = "72h"

just wanna check after upgrade, will there be any impact due to this?

[tawdry geode]

Old configs will continue to work as before 🎉

[scarlet yarrow]

on different note, what is motivation to provide cli bin path feature for customer,_EXPERIMENTAL_DAGGER_CLI_BIN because sdk is downloading already if not provided, so apart from saving network calls, what else do you think it could help 🙂

[tawdry geode]

🤔 this is a totally different thing from the cache

but this is mostly an internal implementation detail, we use it for testing

i wouldn't rely on it, it's undocumented for a reason 🙂

[scarlet yarrow]

i am just reading it here - https://docs.dagger.io/faq/#what-compatibility-is-there-between-the-dagger-engine-dagger-sdks-and-dagger-cli-versions

it also cached by sdk, i read this somewhere in docs

my initial query to understand what is usecase of having such feature 🙂

will there be any case where we need to keep sdk version, cli version and engine different than each other

[tawdry geode]

not really

this is generally not a recommended setup