Allow to execute post update script for every project

Allow executing post-update scripts for every project.

manifest:
  ...
  projects:
    ...
    - name: test
      post-update: post-update.sh

Or

manifest:
  ...
  projects:
    ...
    - name: test
      post-update:
        - post_update1.sh
        - post_update2.sh

The script should be runned just after the update of the particular project and before next projects being updated. When multiple scripts are provided they should be executed in order of presence.

[tejlmand]

just a small note on this. Although for sure a valuable feature, we must be very careful not to execute any arbitary code as part of west update. This could become a security risk on peoples machines.

Currently, commands invoked by users can be verified before execution, such as west update and west build, as the code for those commands are already available in the local system.

But users has no way of verifying code executed as post-update, if it is fetched and executed automatically.

Comparing to git, this is also why, users must install git-hooks themselves, and you cannot force a git-hook onto another persons machine.

[mbolivar]

Thanks! So you’re saying:

• A == openthread
• Dir_aa == vendor/drivers/802.15.4
• openthread requires a literal copy of every driver in its main tree, so Dir_aa in upstream openthread is a latest stable version
• you want to maintain an openthread downstream where Dir_aa is a beta version

I’m not sure this problem should be solved using west. That feels like bending over backwards to allow openthread to remain a monorepo project, instead of allowing its pluggable dependencies (such as 802.15.4 drivers) be maintained out of tree.

I would say that this monorepo requirement is the real problem here, and it is (predictably) leading to the usual version skew problems that come with such requirements. We designed west exactly to avoid having to deal with things like this in Zephyr.

Why not add a patch to the openthread build system to pick Dir_aa_stable or Dir_aa_beta in your downstream openthread instead? Perhaps using a cmake variable?