"Run process" recipe?

[Bananeweizen]

I've experienced several times that I would like to add some final step to a declarative recipe, for which no recipe exists, but which would be doable by calling some external command (current case: git renormalize after modifying .gitattributes via OpenRewrite). Is there anything like a "call external process" recipe? Wouldn't that be generally useful?
Of course I can call that external process without OpenRewrite. But depending on the automation and scheduling around OpenRewrite, it would simplify not touching that remaining infrastructure, as this process would be triggered like any other recipe.

[timtebeek]

hi! To a point we already support something similar through our NodeBasedRecipe class. Do note that it writes the files in the LST to a separate working directory, as opposed to executing in the repository root itself.

For now we don't see ourselves adding an execute-arbitrary-command recipe, as that could lead to some hard to maintain workflows, as well as potential security issues. Instead we'll pull into recipes what makes sense, and continue to expand what we can cover in that way.

If you were to want to write and maintain such a recipe yourself I suggest you similarly create a ScanningRecipe, and run your command in the generate phase to execute it once. I hope that helps!