Connection lifecycle

Driver resolution, connection-string processing, validation, normalization, and masking after ConnectionProperties are populated. Full detail: BeepDM/.cursor/connection/SKILL.md.

Helper façade

ConnectionHelper coordinates driver linking, placeholder replacement, path normalization, validation, and masking (see skill for sub-helpers).

Typical workflow

  1. Start from populated ConnectionProperties.
  2. Resolve driver (GetBestMatchingDriver / linking helpers).
  3. Replace template placeholders; normalize file paths for file-based providers.
  4. Validate; mask secrets in logs; persist through ConfigEditor.

Family-specific notes

Validation and URL shapes differ by DataSourceType (RDBMS host/database, warehouse OAuth, WebAPIConnectionProperties for SaaS, …). See Data providers and, for REST connectors, flagship conn-* pages.

ConnectionProperties IDataSource