v0.3.1

What's New

Per-environment overrides for connections — Connections now support env override maps, matching the existing pattern for sources, destinations, and transformations.

Example

{
  "connections": [{
    "name": "ingest-to-backend",
    "source": "ingest",
    "destination": "backend",
    "filter": {"headers": {"x-env": "default"}},
    "transformations": ["anonymizer"],
    "env": {
      "staging": {
        "filter": {"headers": {"x-env": "staging"}}
      },
      "production": {
        "filter": {"headers": {"x-env": "production"}},
        "transformations": []
      }
    }
  }]
}

Changes

• Added ConnectionOverride type and Env field to ConnectionConfig
• Added ResolveConnectionEnv() resolver following the destination override pattern
• Wired connection env resolution into both manifest and project deploy paths
• Updated JSON schema with connectionOverride definition
• Empty [] for transformations or rules explicitly clears the base value