Hey Meltano team, today our prod got redeployed a...
# troubleshooting
j
Hey Meltano team, today our prod got redeployed and there was a surprise hidden. Our main schedule stopped working. We found out that itโ€™s because we were missing env var
TARGET_SNOWFLAKE_USER
in the config. I see that 5 days ago, there was this commit (1498bf59afa5a9eb44059a6a4f550caab4e07c31) by MeltyBot. The schedule used to work since we had
SF_USER
set. What was the logic behind removing
env_aliases
? Are you sure that no other meltano users are using aliases that all of a sudden stop working?
a
@jozef_reginac - Thanks for reporting this. In fact, this was intended to be a breaking change in upcoming 2.0 which we are messaging here. This was not intended to affect pre-2.0 versions and we will log as an urgent bug.
j
Awesome, I had the feeling that it might be related to v2. Thanks for logging it!
a
@jozef_reginac - I merged a hotfix - as noted here: https://github.com/meltano/meltano/issues/6049#issuecomment-1148592335
If you are able to confirm that this restores normal behavior for you (or not), this would be much appreciated. Thanks!
j
I just tried it and this is what I got from elt run:
Copy code
2022-06-08T06:02:34.881715Z [warning  ] The `discovery.yml` manifest received from <https://discovery.meltano.com/discovery.yml> has version 22, while this version of Meltano requires version 20.
2022-06-08T06:02:34.881921Z [warning  ] Please install the latest compatible version of Meltano using `meltano upgrade`.
and when I ran
meltano upgrade
I got this
Copy code
2022-06-08T06:03:27.808515Z [error    ] The `discovery.yml` manifest received from <https://discovery.meltano.com/discovery.yml> could not be parsed.
So it looks discovery.yml is still not okay, am i right?
a
Hi, @jozef_reginac - Sorry, this message is admittedly confusing. Two points... First - at the time you ran
meltano upgrade
, we may not have had 2.0 out yet. (But it is out now! ๐Ÿš€ ) Second - this is more of a warning or a notice than it is an error. (Again, sorry for the confusion.) Even if Meltano cannot find the file from discovery.meltano.com, there's still a bundled copy installed with pip, so you should be okay regardless.
Is this helpful at all?
j
Yes, I can confirm today we ran pipelines with the warning but without any issue. Thanks @aaronsteers for your help!
a
Glad to hear it @jozef_reginac! Thanks for confirming. ๐Ÿ‘