Open jtomkiew-mng opened 3 months ago
Hi @jtomkiew-mng, thanks for reporting this. The scenario you described is actually a limitation for actions using docker container. Allowing mapping custom local paths to container paths may be a potential feature for azure/cli.
Regarding the github.action_path
, it is only used in composite actions. So far, it hasn't been considered in this action. I will explore ways to achieve this and update you here if there are any developments regarding this issue.
Description
Due to
azure/cli
action script running in a docker container and only mapping current work directory, it seems clunky to use within custom GitHub actions that define resources (i.e. files in the same root directory as the action), as action resources are downloaded to a different directory (github.action_path
), outside of current work directory.The bug part
If you want to consider this a bug, then I would expect all GitHub standard paths to be mapped inside the container (other than the work directory:
github.action_path
and possiblygithub.event_path
, maybe even more, see: https://docs.github.com/en/actions/learn-github-actions/contexts#github-context).The feature part
If you want to consider this a feature request, then I would kindly ask for adding an additional input that allows mapping custom local paths to container paths.
The workaround
To use custom action resources you need to copy them in a separate step to some path in the work directory.