Local development in werf v1.2: even simpler & more convenient

[shurup]

Last week, we have improved the local development support in werf v1.2 in terms of Giterminism limitations. These changes are introduced to help new werf v1.2 users benefit from using local development faster & easier.

Dev mode (--dev)

werf now boasts a simple mode for debugging/development purposes without Giterminism complications and intermediate commits headache. This mode can be enabled via --dev option and works as intended (using the working tree state of your Git repo) with no additional actions required.

You can also switch to the index state by changing the simple mode to strict (--dev-mode=strict).

Following mode (--follow)

This mode allows you to automatically re-execute a command when your Git repo is modified. The command will be executed when a new commit arrives.

If the development mode (--dev) is also enabled, it also watches for the changes in the index of your Git repo.

$ # werf build/converge/composer up/run --follow
$ werf build --follow --dev
┌ Commit "fe7d7ad168d9b4bfdb50f1a4c6326085981c7d26" IndexStatusChecksum "81798fbd"
│ Using werf config render file: /tmp/werf-config-render-073342395
│
│ ┌ ⛵️ image app
│ │ Use cache image for app/from
│ │       name: project:85279ff0e1713f78e68b4356b2fa6a889e85b260e1ba7cf8d3ea09d3-1614264154585
│ │       size: 5.4 MiB
│ │
│ │ Use cache image for app/gitArchive
│ │       name: project:1f3fb53abb5cbc1a3e383160547d79cdd5bdd7932c08316bf0882946-1614346487247
│ │       size: 5.5 MiB (+138.0 KiB)
│ │
│ │ Use cache image for app/setup
│ │       name: project:2140362c4e011034b975aeac498e0c4f52b587f0aece6da1b8d819e2-1614697354869
│ │       size: 5.5 MiB (+2 B)
│ │
│ │ Use cache image for app/gitLatestPatch
│ │       name: project:6ce3ec968266c6d92acf095c76b3af44c5e2cd6d2cc5dbd38d4737f0-1614865470012
│ │       size: 5.5 MiB (+86 B)
│ └ ⛵️ image app (0.02 seconds)
└ Commit "fe7d7ad168d9b4bfdb50f1a4c6326085981c7d26" IndexStatusChecksum "81798fbd" (0.27 seconds)

Waiting for the new commit or staged changes ...

Currently, we don't think a command needs to be executed on each change, thus we suggest to explicitly define a trigger action (commit or git add/rm/...) as the most efficient and convenient method. However we are open for your feedback and other cases to consider!

Both revamped features are currently available in werf v1.2 alpha that is accessible via: source $(multiwerf use 1.2 alpha --as-file)