Environment Variables & Connection References

Purpose: emit environment variables + connection references so one solution moves cleanly across dev/test/prod -- the ALM parameterization layer. No environment-specific value should be hardcoded in an app or flow.

When to Use

• Any value that differs per environment: API base URLs, IDs, feature flags, secrets
• Decoupling flows from specific connections so importers bind their own
• Reviewing a solution for hardcoded environment-specific values before export

Environment Variables

Two parts: a definition (schema name, display name, type, default) and an optional current value (this environment's value). Ship the definition + a default in the solution; let each environment override the current value.