Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stash: external-hooks - 'safe_path' needs to be set #25

Open
natemccurdy opened this issue Jan 30, 2016 · 0 comments
Open

Stash: external-hooks - 'safe_path' needs to be set #25

natemccurdy opened this issue Jan 30, 2016 · 0 comments

Comments

@natemccurdy
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant