Skip to main content
Use the @bijection/connectors/azure-devops entrypoint to declare Azure DevOps resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Work items

pull: WIQL watermark, recycle-bin withdrawal and a state change conditioned on rev

The following example matches configuration standard.

Configuration: standard

Case: azure-devops/workItems/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: azure-devops. Keep credential material in the private credential inventory. Provider setup requirements:
Native admission analysis is available for this exact declaration. Collection: workItems
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: writes

Case: azure-devops/workItems/pull/writes. Connection and resource configuration are declared by this exact case. Credential kind: azure-devops. Keep credential material in the private credential inventory. Provider setup requirements:
Native admission analysis is available for this exact declaration. Collection: workItems
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Git repositories

pull: Repository metadata with deleted-repository withdrawal

The following example matches configuration standard.

Configuration: standard

Case: azure-devops/repositories/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: azure-devops. Keep credential material in the private credential inventory. Provider setup requirements:
Native admission analysis is available for this exact declaration. Collection: repositories
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Pipeline runs

pull: Completed builds by finish time

The following example matches configuration standard.

Configuration: standard

Case: azure-devops/pipelineRuns/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: azure-devops. Keep credential material in the private credential inventory. Provider setup requirements:
Native admission analysis is available for this exact declaration. Collection: pipelineRuns
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

One project of an Azure DevOps Services organization: work items, Git repositories and completed pipeline runs, declared from the Microsoft Learn REST 7.1 reference. Nothing here has run against Azure DevOps. Compiled declaration examples and configuration details are published in the connector reference.
  • Work items are read by a WIQL watermark on System.ChangedDate (timePrecision=true, 200 ids per page) and a workitemsbatch read asOf the query’s own instant. The boundary is re-read. A work item’s version is its integer rev, which every update increments. More than 200 work items changed at one instant is refused. A deleted work item leaves every query, so deletion is read by the reconciliation sweep, and only from the recycle bin’s own entry for the id.
  • Repositories are the deleted-repository listing (withdrawals) followed by the repository listing. No coverage is claimed: the listing is permission-filtered.
  • Pipeline runs are completed builds in finishTimeAscending order, following the x-ms-continuationtoken header, with the latest finish time carried between passes. deleted: true withdraws.
workItems.pull({ governingRule, states }) adds setState, a single-field JSON Patch of System.State limited to the listed states. It is conditioned on the observed version: the patch opens with {"op":"test","path":"/rev", "value":<rev>}, the version rendered as the JSON integer it was read from, so a work item changed since it was observed is not overwritten. A failed test’s status is not documented; 409 and 412 are both refusals. A lost reply stays unknown. Bind the organization and project as setup and keep the credential (a personal access token as Basic with an empty user, or a Microsoft Entra bearer) in native credential custody: Compiled declaration examples and configuration details are published in the connector reference. Package replay is not live qualification. See the generated catalog for exact declared scenarios and evidence status.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.