Question: is it safe to revert from 2.7.1 to 2.5? I'm having a problem in production, and just as a quick fix I want to edit my image version back to when it worked (while I investigate the root cause)

likely not because there were some database migrations that happened… @cody_hanson @aaronsteers can you chime in?

I'm also guessing not because sql alchemy is screaming at me that I don't have the proper db version. Our issue here is that since upgrade to 2.7.1 (without passing by 2.6) everything works locally, but when pushing to code pipeline our deployment fails, which is strange

No, I don't believe we have an automated method for reverting. You could manually downgrade the db and then 2.5 will work, no data is lost or irreversibly changed during the 2.7.1 migration.

@Stéphane Burwash - Sorry to hear you are having difficulties with the latest version. We're here to support if you have any logs on the production-side issue and need assist on that - feel free to log an issue and tag us, and we'll mark has 'high urgency' if it's creating a problem in production. We also just released 2.7.2 which has two small fixes. Calling it out, in case those are related at all to your issue.

@aaronsteers the more I investigate the more I'm thinking this is an issue unrelated to meltano, just a byproduct of upgrading our version (e.g. rebuilding the image file). Will keep you updated though

Ok, thanks! 🙏

@aaronsteers do you know of any reason why a meltano build (when running the command

meltano ui

) would output nothing and timeout?