[
https://issues.apache.org/jira/browse/IMPALA-14287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18028165#comment-18028165
]
ASF subversion and git services commented on IMPALA-14287:
----------------------------------------------------------
Commit 570ab71c9d91f034ad8dc59d48b482a52b28fb50 in impala's branch
refs/heads/master from Peter Rozsa
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=570ab71c9 ]
IMPALA-14287: Resolve environment variables in REST server configurations
This change adds a step to REST server configuration loading that
resolves environment variables noted as ${ENV:VARIABLE_NAME} format. If
the environment variable is not set, then the reference text remains the
same and Impala logs an error.
Tests:
- unit tests added
Change-Id: I3faccc15d012c389703c58371a4d38cca82bef60
Reviewed-on: http://gerrit.cloudera.org:8080/23457
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Support environment variables in MetaProvider configurations
> ------------------------------------------------------------
>
> Key: IMPALA-14287
> URL: https://issues.apache.org/jira/browse/IMPALA-14287
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Reporter: Peter Rozsa
> Assignee: Peter Rozsa
> Priority: Major
> Labels: impala-iceberg
>
> MetaProvider configuration .properties files should support environment
> variables, for example:
> connection-password=${ENV:DB_PASSWORD}
> where DB_PASSWORD should be read as an environment variable.
> This helps secret management in configurations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
