[
https://issues.apache.org/jira/browse/IGNITE-25752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-25752:
----------------------------------------
Fix Version/s: 3.2
(was: 3.1)
> Add environment variable configuration mechanism
> ------------------------------------------------
>
> Key: IGNITE-25752
> URL: https://issues.apache.org/jira/browse/IGNITE-25752
> Project: Ignite
> Issue Type: Improvement
> Components: configuration ai3
> Reporter: Pavel Tupitsyn
> Priority: Major
> Labels: ignite-3
> Fix For: 3.2
>
>
> As a user, I'd like to set Ignite *node configuration* with *environment
> variables*. This is very useful in containerized environments (Docker, k8s),
> cloud-native deployments, and also for demos and POCs.
> Dealing with config files in those scenarios can be cumbersome. Env vars are
> widely used instead.
> h2. Example
> {code}
> docker run -p 10300:10300 -p 10800:10800 -e
> IGNITE_CLIENTCONNECTOR_IDLETIMEOUTMILLIS=9000 -e
> IGNITE_SQL_EXECUTION_THREADCOUNT=8 apacheignite/ignite:3.1.0
> {code}
> h2. Requirements
> * Any node configuration property can be set with an environment variable
> * Env var name is derived from property path: *prop.replace(".",
> "_).toUpper()*: "ignite.sql.threadCount" -> "IGNITE_SQL_THREADCOUNT" (upper
> snake case is a common convention for env vars)
> * Does not apply to cluster configuration properties
> * Disabled by default
> * Can be enabled with *IGNITE_CONFIG_ENV_VARS=true*
> * Enabled in Ignite Docker image by default
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
