-
-
Notifications
You must be signed in to change notification settings - Fork 998
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
REST Api feature #19
Comments
There is a JSON api already written which the frontend code uses. The authentication mechanism would need to change to allow scripts easier access. For the short-term, you could use the Cookie header as authentication. Better API access will definitely be looked at (0-2 weeks?). Endpoint that starts a job: /lib/routes/task/tasks.js#L60 Try this with curl:
|
+1 Is there a way that basic token authentication can be implemented? |
Yeah instead of using cookies it could accept an What will take some time is API documentation :). I suppose we'll start a wiki for that. |
Is there anything I can do to help? I haven't created a nodejs app before but I can write documentation :) |
You already did. Nudge me to do this :P |
I'll let you know once it works and we can collaborate on the documentation. Thanks for offering |
This would be very nice, an additional function that would be great if it worked is:
|
V2 documentation here: https://ansible-semaphore.github.io/semaphore V2-alpha can be downloaded from the releases page. |
I've been playing with semaphore for a while now. Good alternative if Ansible Tower isn't an option.
One feature that I'd like to see is a REST API so that it would be possible to fire off playbooks via an API. Would this be possible / been looked at?
Cheers.
The text was updated successfully, but these errors were encountered: