Hey All! Could you please help us? When we change something in the cfg of Airflow is not automatically reflected by Meltano? We restarted the ariflow webserver but seems not reflecting the change in the cfg. to give more context: when we try to update the airflow configuration locally (meltano.yml) the only way it will take effect is by deleting the ".meltano/" folder and then running "meltano install" command again. I'm not sure if it's a bug related to the version of meltano deployed or we are missing something. Version 1.105.0

👋 Hi Tomas. Off the top of my head, I'm not sure what could be causing this. Let me see if I can reproduce the issue and then I'll investigate further.

Thnaks @cody_hanson, let me know. I will stay tunned here.

Could you also provide some additional context? Particularly: 1. What Airflow config setting(s) have you had this issue with? 2. Have you successfully configured Airflow using

meltano config

in the past and this behavior is new? If so--did this start occurring after an upgrade or reinstall? Or is this your first time configuring Airflow using Meltano? 3. What Python version are you running?

Hi @cody_hanson thanks for your help: 1 - we are trying to activate airflow API access: api.auth_backend: airflow.api.auth.backend.basic_auth We tried with other configs related to the airflow webserver and had the same issue (it has no effect until reinstall) 2 - first time 3. - 3.7

Thanks for the additional info here. I'm able to reproduce this issue on my machine. @david_rojas I'm also seeing the same

No such file or directory

error that you described when I try to do

meltano config airflow list

. Unfortunately, it seems like this behavior is persisting even after upgrading to the latest version. I've opened this bug report to track. Please feel free to add any additional context you can think of to that issue.

@cody_hanson I havent had this issue. Locally I use

env

vars like https://github.com/meltano/squared/blob/b1bef50cc1d7c7e8bf0ffc79246f498e6b7bca49/data/environments/userdev.meltano.yml#L67 and in production we use the default helm chart and havent had to make any config changes so I dont know exactly how that would work