I was adding Lean runtime support to ado-aw, and the hardest part was figuring out how to inject runtime paths into awf. There is quite a lot of path sanitisation in that flow, and the existing implementation appears to have built-in support for GITHUB_PATH, which makes sense for GitHub runners. The agent struggled to find the right integration point for Azure DevOps runners, which use mostly the same underlying model but do not provide the GITHUB_PATH variable. I eventually had to dig through the implementation myself to identify the right place to add the ADO-specific path handling.
It would be great at the very minimum to have docs that record this integration point.
I was adding Lean runtime support to ado-aw, and the hardest part was figuring out how to inject runtime paths into awf. There is quite a lot of path sanitisation in that flow, and the existing implementation appears to have built-in support for GITHUB_PATH, which makes sense for GitHub runners. The agent struggled to find the right integration point for Azure DevOps runners, which use mostly the same underlying model but do not provide the GITHUB_PATH variable. I eventually had to dig through the implementation myself to identify the right place to add the ADO-specific path handling.
It would be great at the very minimum to have docs that record this integration point.