You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Zelko Nikolic (JIRA)" <ji...@apache.org> on 2017/11/28 22:17:00 UTC
[jira] [Created] (AIRFLOW-1861) If a variable is lowercase and
contains words like "secret" it is encrypted, but if variable is uppercase,
then it's not encrypted
Zelko Nikolic created AIRFLOW-1861:
--------------------------------------
Summary: If a variable is lowercase and contains words like "secret" it is encrypted, but if variable is uppercase, then it's not encrypted
Key: AIRFLOW-1861
URL: https://issues.apache.org/jira/browse/AIRFLOW-1861
Project: Apache Airflow
Issue Type: Bug
Affects Versions: Airflow 1.8
Reporter: Zelko Nikolic
This is such a big inconsistency that it's basically a bug. Concluding whether a variable should be encrypted or not shouldn't even be decided by its name, even less by its case.
There should be a checkbox so when one clicks it, the variable is encrypted, otherwise it's not. But the way it works now, making this feature case-sensitive, is inexplicable. Why would someone do something like that????
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)