Twenty-one systems. Two are exercised against the real thing in CI, and vault against a real Vault
in Docker when one is available; most validate every request their tests make against the vendor's
published API description; none has yet been confirmed against a live account. The live test
(examples/live-cases.yaml,
how to run it) is there for you to run against
your own systems before you rely on an integration. Every integration's docs
end with an Unverified section naming what has not been confirmed; for the six marked beta
that list is long enough that you should read it first.
| Integration | Status | Tests run against |
|---|---|---|
| kubernetes | ready | a real cluster (kind), end to end |
| argocd | ready | the real argocd CLI evaluator (differential test) |
| github | ready | fake upstream, requests validated against GitHub's API description |
| gitlab | ready | fake upstream, validated against GitLab's API description |
| bitbucket (Cloud and Data Center) | ready | fake upstream, validated against Bitbucket Cloud's API description |
| jira (Cloud) | ready | fake upstream, validated against Jira's API description |
| confluence (Cloud) | ready | fake upstream, validated against Confluence's API descriptions |
| slack | ready | fake upstream, validated against Slack's API description |
| datadog | ready | fake upstream, validated against Datadog's API descriptions |
| pagerduty | ready | fake upstream, validated against PagerDuty's API description |
| aws | ready | fake upstream, validated against the IAM, STS and Identity Center service models |
| googleworkspace | ready | fake upstream, validated against the Google API discovery documents |
| googlecloud | ready | fake upstream, validated against the Policy Troubleshooter discovery document |
| microsoft365 | ready | fake upstream, validated against the Microsoft Graph API description |
| databricks | ready | fake upstream only |
| salesforce | beta | fake upstream only; see Unverified in its docs |
| snowflake | beta | fake upstream, validated against the SQL API description; see Unverified |
| vault | beta | fake upstream, validated against Vault's API description, and a real Vault dev server in Docker; see Unverified |
| azure | beta | fake upstream, validated against the Azure authorization API descriptions; see Unverified |
| linear | beta | fake upstream, validated against Linear's GraphQL schema; see Unverified |
| zendesk | beta | fake upstream, validated against Zendesk's API description; see Unverified |
| fake | for smoke tests |
Each page covers the credential to create, the minimum permissions it needs, how the email maps to
an account, the actions and resources, and what it cannot see. toolpass catalog <integration>
prints the same keys and actions from the installed package. To add a system, see
integration authoring.