You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "jack (JIRA)" <ji...@apache.org> on 2019/07/04 15:27:00 UTC

[jira] [Updated] (AIRFLOW-4898) Variable change log

     [ https://issues.apache.org/jira/browse/AIRFLOW-4898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jack updated AIRFLOW-4898:
--------------------------
    Description: 
Airflow doesn't expose log of changes that made on Variables.

 

It would be great if this will be exposed as log in the UI.

Something like:

variable name  | time of change |  old value | new value | changed by 

 

changed by can be by dag_id if it's done with a DAG run or user_id if it was changed manually from the UI /CLI by user.

Maybe even have this ability set on/off on Variable level rather than globally so the user can decide if changes of variables will be saved to log or not. This will help in preventing spam over the log for variables that have no interest to the user.

  was:
Airflow doesn't expose log of changes that made on Variables.

 

It would be great if this will be exposed as log in the UI.

Something like:

variable name  | time of change |  old value | new value | changed by 

 

changed by can be by dag_id if it's done with a DAG run or user_id if it was changed manually from the UI /CLI by user


> Variable change log
> -------------------
>
>                 Key: AIRFLOW-4898
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4898
>             Project: Apache Airflow
>          Issue Type: Wish
>          Components: core, ui
>    Affects Versions: 1.10.4
>            Reporter: jack
>            Priority: Major
>
> Airflow doesn't expose log of changes that made on Variables.
>  
> It would be great if this will be exposed as log in the UI.
> Something like:
> variable name  | time of change |  old value | new value | changed by 
>  
> changed by can be by dag_id if it's done with a DAG run or user_id if it was changed manually from the UI /CLI by user.
> Maybe even have this ability set on/off on Variable level rather than globally so the user can decide if changes of variables will be saved to log or not. This will help in preventing spam over the log for variables that have no interest to the user.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)