You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Sergio Kef (Jira)" <ji...@apache.org> on 2019/11/20 09:37:00 UTC
[jira] [Commented] (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
[ https://issues.apache.org/jira/browse/AIRFLOW-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978258#comment-16978258 ]
Sergio Kef commented on AIRFLOW-1861:
-------------------------------------
I don't get what this is about. [~zexerlang] can you provide some more info?
Is this about variables in connections? AFAIK only passwords are encrypted in connections.
> 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: 1.8.0
> Reporter: Zelko Nikolic
> Priority: Major
>
> 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
(v8.3.4#803005)