Does Karate automatically map process.env.KARATE_ENV to karate.env in CI?

In Karate, the karate-config.js file typically uses the karate.env variable to assign a baseUrl based on the target environment (e.g., dev, staging, or prod). While this configuration works reliably during local execution where the environment is explicitly passed, it can lead to failures in production or CI/CD pipelines if the variable is not correctly resolved.

In containerized environments, there is often a discrepancy between system-level environment variables and the variables accessible within the Karate framework. While newer versions of Karate 1.x and 2.x provide access to process.env, it is unclear if karate.env is automatically populated from process.env.KARATE_ENV without explicit mapping logic inside the configuration file.

Which mechanism is recommended to ensure the baseUrl is correctly resolved when the execution context changes from local to CI? Does Karate provide a built-in fallback that maps system environment variables to karate.env, or must this be manually implemented in karate-config.js?