How to avoid the 'masking' of directorynames with ***

[waardd]

When runnning a dag that does something with directories like the example below, the directory gets 'masked' with ***
How do i turn this off?
In this example it looks like its masking the term airflow

[2024-04-24, 07:22:33 CEST] {taskinstance.py:1300} INFO - Executing <Task(BashOperator): log_cleanup_worker_num_1_dir_0> on 2024-04-24 05:22:31.181751+00:00
[2024-04-24, 07:22:33 CEST] {standard_task_runner.py:55} INFO - Started process 2062930 to run task
[2024-04-24, 07:22:33 CEST] {standard_task_runner.py:82} INFO - Running: ['***', 'tasks', 'run', '***_log_cleanup', 'log_cleanup_worker_num_1_dir_0', 'manual__2024-04-24T05:22:31.181751+00:00', '--job-id', '464974', '--raw', '--subdir', 'DAGS_FOLDER/***_log_cleanup.py', '--cfg-path', '/tmp/tmpgf19ifvx']
[2024-04-24, 07:22:33 CEST] {standard_task_runner.py:83} INFO - Job 464974: Subtask log_cleanup_worker_num_1_dir_0
[2024-04-24, 07:22:34 CEST] {task_command.py:388} INFO - Running <TaskInstance: airflow_log_cleanup.log_cleanup_worker_num_1_dir_0 manual__2024-04-24T05:22:31.181751+00:00 [running]> on host lste001440.eu.rabonet.com
[2024-04-24, 07:22:34 CEST] {taskinstance.py:1507} INFO - Exporting the following env vars:
AIRFLOW_CTX_DAG_EMAIL=fm.nl.its.rf.abusemca@rabobank.nl
AIRFLOW_CTX_DAG_OWNER=operations
AIRFLOW_CTX_DAG_ID=***_log_cleanup
AIRFLOW_CTX_TASK_ID=log_cleanup_worker_num_1_dir_0
AIRFLOW_CTX_EXECUTION_DATE=2024-04-24T05:22:31.181751+00:00
AIRFLOW_CTX_TRY_NUMBER=1
AIRFLOW_CTX_DAG_RUN_ID=manual__2024-04-24T05:22:31.181751+00:00
[2024-04-24, 07:22:34 CEST] {subprocess.py:63} INFO - Tmp dir root location: 
 /tmp
[2024-04-24, 07:22:34 CEST] {subprocess.py:75} INFO - Running command: ['/usr/bin/bash', '-c', '\n\necho "Getting Configurations..."\nBASE_LOG_FOLDER="/appl/mca/log/***"\nWORKER_SLEEP_TIME="3"\n\nsleep ${WORKER_SLEEP_TIME}s\n\nMAX_LOG_AGE_IN_DAYS=""\nif [ "${MAX_LOG_AGE_IN_DAYS}" == "" ]; then\n    echo "maxLogAgeInDays conf variable isn\'t included. Using Default \'30\'."\n    MAX_LOG_AGE_IN_DAYS=\'30\'\nfi\nENABLE_DELETE=true\necho "Finished Getting Configurations"\necho ""\n\necho "Configurations:"\necho "BASE_LOG_FOLDER:      \'${BASE_LOG_FOLDER}\'"\necho "MAX_LOG_AGE_IN_DAYS:  \'${MAX_LOG_AGE_IN_DAYS}\'"\necho "ENABLE_DELETE:        \'${ENABLE_DELETE}\'"\n\ncleanup() {\n    echo "Executing Find Statement: $1"\n    FILES_MARKED_FOR_DELETE=`eval $1`\n    echo "Process will be Deleting the following File(s)/Directory(s):"\n    echo "${FILES_MARKED_FOR_DELETE}"\n    echo "Process will be Deleting `echo "${FILES_MARKED_FOR_DELETE}" |     grep -v \'^$\' | wc -l` File(s)/Directory(s)"         # "grep -v \'^$\'" - removes empty lines.\n    # "wc -l" - Counts the number of lines\n    echo ""\n    if [ "${ENABLE_DELETE}" == "true" ];\n    then\n        if [ "${FILES_MARKED_FOR_DELETE}" != "" ];\n        then\n            echo "Executing Delete Statement: $2"\n            eval $2\n            DELETE_STMT_EXIT_CODE=$?\n            if [ "${DELETE_STMT_EXIT_CODE}" != "0" ]; then\n                echo "Delete process failed with exit code                     \'${DELETE_STMT_EXIT_CODE}\'"\n\n                echo "Removing lock file..."\n                rm -f /tmp/***_log_cleanup_worker.lock\n                if [ "${REMOVE_LOCK_FILE_EXIT_CODE}" != "0" ]; then\n                    echo "Error removing the lock file.                     Check file permissions.                    To re-run the DAG, ensure that the lock file has been                     deleted (/tmp/***_log_cleanup_worker.lock)."\n                    exit ${REMOVE_LOCK_FILE_EXIT_CODE}\n                fi\n                exit ${DELETE_STMT_EXIT_CODE}\n            fi\n        else\n            echo "WARN: No File(s)/Directory(s) to Delete"\n        fi\n    else\n        echo "WARN: You\'re opted to skip deleting the File(s)/Directory(s)!!!"\n    fi\n}\n\n\nif [ ! -f /tmp/***_log_cleanup_worker.lock ]; then\n\n    echo "Lock file not found on this node!     Creating it to prevent collisions..."\n    touch /tmp/***_log_cleanup_worker.lock\n    CREATE_LOCK_FILE_EXIT_CODE=$?\n    if [ "${CREATE_LOCK_FILE_EXIT_CODE}" != "0" ]; then\n        echo "Error creating the lock file.         Check if the *** user can create files under tmp directory.         Exiting..."\n        exit ${CREATE_LOCK_FILE_EXIT_CODE}\n    fi\n\n    echo ""\n    echo "Running Cleanup Process..."\n\n    FIND_STATEMENT="find ${BASE_LOG_FOLDER}/*/* -type f -mtime      +${MAX_LOG_AGE_IN_DAYS}"\n    DELETE_STMT="${FIND_STATEMENT} -exec rm -f {} \\;"\n\n    cleanup "${FIND_STATEMENT}" "${DELETE_STMT}"\n    CLEANUP_EXIT_CODE=$?\n\n    FIND_STATEMENT="find ${BASE_LOG_FOLDER}/*/* -type d -empty"\n    DELETE_STMT="${FIND_STATEMENT} -prune -exec rm -rf {} \\;"\n\n    cleanup "${FIND_STATEMENT}" "${DELETE_STMT}"\n    CLEANUP_EXIT_CODE=$?\n\n    FIND_STATEMENT="find ${BASE_LOG_FOLDER}/* -type d -empty"\n    DELETE_STMT="${FIND_STATEMENT} -prune -exec rm -rf {} \\;"\n\n    cleanup "${FIND_STATEMENT}" "${DELETE_STMT}"\n    CLEANUP_EXIT_CODE=$?\n\n    echo "Finished Running Cleanup Process"\n\n    echo "Deleting lock file..."\n    rm -f /tmp/***_log_cleanup_worker.lock\n    REMOVE_LOCK_FILE_EXIT_CODE=$?\n    if [ "${REMOVE_LOCK_FILE_EXIT_CODE}" != "0" ]; then\n        echo "Error removing the lock file. Check file permissions. To re-run the DAG, ensure that the lock file has been deleted (/tmp/***_log_cleanup_worker.lock)."\n        exit ${REMOVE_LOCK_FILE_EXIT_CODE}\n    fi\n\nelse\n    echo "Another task is already deleting logs on this worker node.     Skipping it!"\n    echo "If you believe you\'re receiving this message in error, kindly check     if /tmp/***_log_cleanup_worker.lock exists and delete it."\n    exit 0\nfi\n']
[2024-04-24, 07:22:34 CEST] {subprocess.py:86} INFO - Output:
[2024-04-24, 07:22:34 CEST] {subprocess.py:93} INFO - Getting Configurations...
[2024-04-24, 07:22:37 CEST] {subprocess.py:93} INFO - maxLogAgeInDays conf variable isn't included. Using Default '30'.
[2024-04-24, 07:22:37 CEST] {subprocess.py:93} INFO - Finished Getting Configurations
[2024-04-24, 07:22:37 CEST] {subprocess.py:93} INFO - 
[2024-04-24, 07:22:37 CEST] {subprocess.py:93} INFO - Configurations:
[2024-04-24, 07:22:37 CEST] {subprocess.py:93} INFO - BASE_LOG_FOLDER:      '/appl/mca/log/***'
[2024-04-24, 07:22:37 CEST] {subprocess.py:93} INFO - MAX_LOG_AGE_IN_DAYS:  '30'
[2024-04-24, 07:22:37 CEST] {subprocess.py:93} INFO - ENABLE_DELETE:        'true'
[2024-04-24, 07:22:37 CEST] {subprocess.py:93} INFO - Lock file not found on this node!     Creating it to prevent collisions...
[2024-04-24, 07:22:37 CEST] {subprocess.py:93} INFO - 
[2024-04-24, 07:22:37 CEST] {subprocess.py:93} INFO - Running Cleanup Process...
[2024-04-24, 07:22:37 CEST] {subprocess.py:93} INFO - Executing Find Statement: find /appl/mca/log/***/*/* -type f -mtime      +30

[Taragolis]

Masking secrets for the passwords is always turned on, and there is no way (without monkey-patching) to disable it.
Just a suggestion, change your DB or some connection password from the airflow to something more secure, in this case it should not mask airflow with *** into the logs

[waardd]

dumb dumb dumb....
This only concerns the password and not the user right?

[Taragolis]

Yep, by default should be only passwords, and some extra fields in Connections or Variables

[waardd]

Okay here the noob questions

How can i change the airflow DB password to something else.
If i change the password for the connection for the airflow user, airflow does no longer work.
(tested on a local postgresql database)
So how can change the password of the connection user and have airdlow still working.
My understanding of the settings is that the password is stored in the database and located by the fernet key.

# Secret key to save connection passwords in the db
fernet_key = <a key>