Technical
Lynx Connectors
Compliance-agnostic framework for saved connections to external systems, with a pluggable per-system registry and a shared REST/JSON client.
lynx_connectors
· v19.0.1.0.0
· Standard
Beta
What this solves
Lynx Connectors
A saved-connection framework any Lynx app can build on. A connection to an external system - a monitoring platform, cloud provider, IdP or SIEM - is configured once as a lynx.connector record and then read by any app through a small Python registry, so the same Zabbix or Datadog connection serves the status page and the compliance evidence collectors alike.
This module holds only the plumbing. Provider modules (lynx_connector_zabbix and friends) register their own type and answer resource queries; consuming apps call connector.list_resources(...) and receive a unified result shape.
Key Features
Connection registry - lynx.connector stores endpoint, credentials and free-form JSON config, one record per external system instance.
Pluggable types - connector types are a Python registry; each provider module registers its own BaseConnector subclass keyed by a stable code.
Shared REST client - RestConnector factors out the JSON-over-HTTPS client, response-shape guards, OAuth2 token exchange and three pagination dialects so a provider supplies only its URLs and auth.
Test-connection action - one-click connectivity check from the form.
Secret indirection - implementations read the secret through _get_secret(), an override hook for a Barbican / Vault backend.
Integrates With
lynx_connector_* - provider-specific implementations.
lynx_status_page - reads component health from a connection.
lynx_compliance_connectors - the compliance evidence bridge builds on it.
Depends on
Try Lynx Connectors on your team.
Free trial, no credit card. Talk to sales when you're ready.