Pipeline Configuration - CircleCI
CircleCI pipeline continuation, pipeline-definition mutation, triggers, schedules, user lookup, and job cancellation by project-local number. Generated from the complete hash-pinned official CircleCI API v2 OpenAPI document. The CircleCI cloud base is the enrollment default; per-organization connections may target a compatible CircleCI Server API v2 base. Reads are uncached and approval-free. Mutations are grant-off and approval-gated; destructive and administrative changes require approval every run.
What this pack installs
- circleci-pipeline-config Ingredient
Trust & control
What installing this whole pack would let it do. Recued grants these permissions at install — review them there before approving.
What it's allowed to do
Destructive
Web APIs
circleci-pipeline-config
external change
Read: list_pipelines · No approvalWrite: continue_pipeline · Asks approvalDestructive: cancel_job_by_job_number · Always asksAdmin: create_schedule · Always asksDestructive: delete_schedule_by_id · Always asksAdmin: update_schedule · Always asksRead: get_user · No approvalAdmin: create_pipeline_definition · Always asksAdmin: update_pipeline_definition · Always asksDestructive: delete_pipeline_definition · Always asksAdmin: create_trigger · Always asksAdmin: update_trigger · Always asksDestructive: delete_trigger · Always asks