Environment variable precedence between CLI and configuration files

Variable Resolution Priority

Jeet utilizes a declarative configuration file to manage build settings and environment variables, while also allowing variable definition via the CLI during the deployment workflow.

When a specific environment variable is defined in both the project configuration file and passed through the CLI, the system must resolve which value takes precedence during the synchronization with the remote edge runtime.

Current documentation does not explicitly define the hierarchy for these overlapping definitions, creating uncertainty during automated deployment pipelines where both sources may be active.

• Does the CLI-provided value override the declarative configuration file?
• Is there a mechanism to lock configuration file values to prevent CLI overrides?