Overview:
Tulip currently ties connector functions to a single environment (Production) once an app is published. However, enterprise workflows require multiple environments—Development, Pre-Production, and Production—to ensure proper testing, approvals, and controlled releases.
The proposed enhancement is to enable different published apps to reuse the same connector while binding to the correct environment.
App-Level Environment Binding (Core Requirement):
-
Each published app should explicitly bind to an environment profile (Dev, Pre-Prod, or Prod) at the time of publishing.
-
This binding determines which environment configuration of the connector is used at runtime.
-
Example:
-
App A (Development)→ Connector uses Dev Environment. -
App B (Pre-Prod)→ Connector uses Pre-Prod Environment. -
App C (Production)→ Connector uses Prod Environment.
-
-
Key Points:
-
The same connector definition and connector functions are reused across all apps.
-
No need to duplicate connectors for each environment.
-
Promotion workflows can simply switch environment binding without changing app logic.
-
Benefits of App-Level Binding:
-
Governance & Control: Prevents accidental use of production endpoints during development or QA.
-
Efficiency: Eliminates connector duplication and manual reconfiguration.
-
Traceability: Clear environment association for each app version.
-
Scalability: Supports enterprise-grade workflows with multiple environments.