---------------------- Garden's smart caching abilities ensure that the same image never needs to be built twice or the same test run twice if the code hasn’t changed. This is due to Garden's ability to calculate the version of any part of your system, while accounting for upstream dependencies. This feature can speed up your pipelines significantly [source ()]. To specify the files to be watched, you can use the

sync

configuration key. This specifies which files or directories to sync to which paths inside the running containers of the service when it's in sync mode. Sync mode can be enabled by setting the

--sync

flag on the

garden deploy

command. This configuration key is available for different module types like jib-container (), container (), kubernetes (), and action-types (). For example, in a Kubernetes module, the configuration would look like this:

yaml
sync:
  paths:
    - containerPath: /app/src
      sourcePath: ${actions.build.vote-image.sourcePath}/src
      mode: two-way

This configuration specifies that the

/app/src

directory inside the running container should be kept in sync with the

src

directory in the

vote-image

build action's directory. The

two-way

mode means that changes in either location are mirrored to the other.

For more information on synchronization, you can check out the Code Synchronization Guide (). ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted