https://garden.io logo
#🌱|help-and-getting-started
'modules.' field deprecation
# 🌱|help-and-getting-started
b

brief-dawn-88958

07/11/2023, 3:59 PM
The migration guide (https://docs.garden.io/tutorials/migrating-to-bonsai#breaking-changes-first) states: > The modules.* field has been renamed to scan.*. The old syntax is still supported with a deprecation warning. I don't see a deprecation warning when using
${modules.mymodule.var.my-var}
in v0.13. Nor does the
${scan.}
field work for me in the context of a module: > Invalid template string (${scan.mymodule.var.my-var}): Could not find key scan. Available keys: command, datetime, environment, git, inputs, local, modules, project, providers, runtime, secrets, this, var and variables. Was the
modules -> scan
renaming only done in the context of the new actions? In the migration guide it sounds like it affects modules as well. Else it wouldn't be a breaking change - would it?
q

quaint-dress-831

07/11/2023, 5:06 PM
I haven't encountered this
scan
field once so this is new to me. @calm-family-29323, do you have the answer?
c

calm-family-29323

07/12/2023, 7:26 AM
I think this is about project level
scan.include
and
scan.exclude
https://docs.garden.io/reference/project-config#scan 0.12 modules -> https://docs.garden.io/v/acorn-0.12/reference/project-config#modules
b

brief-dawn-88958

07/12/2023, 7:28 AM
I see. that makes sense. Thanks for clarification.