Approve workflows via API
complete
A
Andrew Haines
Right before we hit the approval step in our workflow, we ping Slack with a link to the workflow so that someone can go into CircleCI to approve. We’d love it if we could respond to our chatops bot and it could approve the job without us having to leave Slack. However, there doesn’t seem to be a public API that exposes the functionality of clicking on the Approve button.
CCI-I-289
Alexey
Thanks everyone for your feedback! The job approval endpoint is now available:https://circleci.com/changelog/#new-api-v2-job-approval-endpoint
d
dokig e
What is the timeline that "On roadmap" represents? quarters/years/centuries?
N
Nathan Evans
What is the timeline that "On roadmap" represents? Weeks/months/quarters?
J
Jitesh Sojitra
Any update on this? We desperately need this API for handling big workflow!
N
Nathan Evans
Same, this is desperately needed
N
Nadeem Shabir
I think this would be a good idea too.
For the person who raised the ticket, how are you pinging the workflow into slack?
Dan Ofir
any update on this?
D
Dana Cleveland
Any update on this? Looking forward to this one, combined with CCI-I-352
S
Saj Janin
- When triggering a job, the workspace context is not available. we can use persist_to_workspace, attach_workspace to share context information between jobs, but this is not possible when using current API. 2. The workflow steps are broken. Once a approval job is trigger (which later triggers another job through API call), subsequent jobs cannot be configured which restricts us to having approvals as the only last step in workflow. We would be able to do Job1->Approve->job2 with context of job2-->approve-->3rd job with the context of job3.
M
Martin Smith
It would also be useful if there was a way to prevent users from approving, and only having an API call be able to approve. We'd like to implement some workflows that have an API approval in them, but don't want users to also be able to go in to approve something manually.
Load More
→