little-army-47606
12/18/2024, 7:13 PMmicroscopic-river-74022
12/18/2024, 7:13 PMmicroscopic-river-74022
12/18/2024, 7:13 PM${runtime.build.<action-name>.mode}
or
${actions.build.<action-name>.mode}
2. For Deploy actions:
${this.mode}
3. For Run actions:
${runtime.run.<action-name>.mode}
4. For Task actions:
${runtime.tasks.<action-name>.mode}
These template strings allow you to reference the mode in your configuration, which could potentially be used for conditional logic or debugging purposes.
It's worth noting that Build actions inherit their mode from Deploy actions that depend on them. For example, if a Deploy action is in 'sync' mode and depends on a Build action, the Build action will inherit the 'sync' mode setting from the Deploy action.
While this information doesn't directly answer how to review the buildMode from logs, it provides context on how the mode is used and accessed within Garden's configuration. To get more specific information about reviewing the buildMode in logs, you might need to consult Garden's documentation on logging or debugging features, which are not covered in the provided knowledge sources.microscopic-river-74022
12/18/2024, 7:13 PMmicroscopic-river-74022
12/18/2024, 7:13 PMmicroscopic-river-74022
12/19/2024, 12:03 AMlittle-army-47606
12/19/2024, 12:03 AMmicroscopic-river-74022
12/19/2024, 12:03 AMmicroscopic-river-74022
12/19/2024, 12:03 AMmicroscopic-river-74022
12/19/2024, 12:03 AM