---------------------- Short answer: not yet. - There isn’t a documented flag or config to suppress a task’s stdout/stderr or hide run-action logs today. An open feature request proposes adding toggles like hide_stdout/hide_stderr; maintainers noted overlap with a separate effort to mark and redact sensitive values. [[FEATURE 6557](); [FEATURE 5666]()] - Work-in-progress: a Secret type was added internally to support redaction when such objects are logged, but templates/helpers to mark values as sensitive across the system are still to come. [[FEATURE 5666]()] Given this, there’s no supported way in the docs to prevent printing task output entirely. If you’re running in CI, you can at least switch to the basic logger to reduce noisy formatting (doesn’t hide content): set GARDEN_LOGGER_TYPE=basic or pass --logger-type=basic. [[Using CLI](); [CircleCI guide]()] If leaking secrets is a risk for your use case, consider avoiding putting secrets in stdout and track the two issues above for upcoming redaction/hiding support. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted

---------------------- Short answer: not directly. - Garden supports varfiles (YAML/JSON/dotenv) at project and action/module level, but the docs only describe loading them from fixed paths configured in project or action config; there’s no documented mechanism to produce a varfile at runtime in one task and have Garden automatically reload and use it in another. [[Project varfile](); [Action varfiles (edge)]()] - You can pass values between tasks via runtime outputs (template keys under runtime.*), but those are for templating within the same run and aren’t described as a way to create or switch varfiles dynamically. [[Runtime outputs]()] Given the docs, a supported pattern would be: - Use runtime outputs to pass computed values directly to dependent steps/tasks within the same run, instead of writing a varfile. [[Runtime outputs]()] - Or, predefine the varfile path(s) in config and write your script to update the file before subsequent commands in the same workflow, but note the docs don’t guarantee Garden will pick up mid-run changes or support generating new paths dynamically. [[Project varfile](); [Workflows]()] If you need stronger guarantees for dynamic config, the knowledge sources don’t provide an explicit, supported method. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted