You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Stash (Bitbucket Server) and the External-Hooks add-on, the git_webhook type is unable to modify (create/change) the parameters for the external-hooks add-on because the safe_path attribute needs to be set when hitting the API.
-X PUT -d '{"exe":"debug.sh", "params":"-a foo", "safe_path":true}'
Specifically, if using a Stash user account that only has admin rights to a project/repo, then the exe executable must be in $STASH_HOME/external-hooks, and the path must be relative to that directory. When doing that, safe_path must be set to true or else the API will not allow the change.
If using a Stash user account that has global admin rights (like the default 'admin' user), then safe_path doesn't need to be managed and the exe does not have to be in the $STASH_HOME/external-hooks directory. In which case an absolute path to the exe should be used.
The text was updated successfully, but these errors were encountered:
When using Stash (Bitbucket Server) and the External-Hooks add-on, the
git_webhook
type is unable to modify (create/change) the parameters for the external-hooks add-on because thesafe_path
attribute needs to be set when hitting the API.Specifically, if using a Stash user account that only has admin rights to a project/repo, then the
exe
executable must be in$STASH_HOME/external-hooks
, and the path must be relative to that directory. When doing that,safe_path
must be set to true or else the API will not allow the change.If using a Stash user account that has global admin rights (like the default 'admin' user), then
safe_path
doesn't need to be managed and theexe
does not have to be in the$STASH_HOME/external-hooks
directory. In which case an absolute path to theexe
should be used.The text was updated successfully, but these errors were encountered: