I wanted to hold off the upgrade to Meltano 2.0 a bit in case there were some small issues, but now I'm getting `The

discovery.yml

manifest received from https://discovery.meltano.com/discovery.yml could not be parsed.` errors so I guess I have no choice 🙃 after upgrading, the workflows that were running fine so far now fail with

Extractor failed: Unrecognized replication_method None

. I did

meltano config tap-postgres--orchest-dashboard set _metadata '*' replication-method FULL_TABLE

again just in case, still fails (which makes sense, because nothing changed in

meltano.yml

).

meltano invoke --dump=catalog tap-postgres

works well too. how can I keep troubleshooting this issue? for reference, I'm invoking

meltano run tap-postgres alias-tables target-postgres

with

pipelinewise-tap-postgres

. changing variant is not an option because the singer one is unmaintained.

@juan_luis_cano_rodriguez As you’ve found, you can ignore the

discovery.yml

warning — we can make that message more scary because using Meltano <2.0 is still totally fine if you don’t have a reason to upgrade, although we of course can’t fix that in Meltano-pre-2.0 that have already been installed... Your existing

meltano.yml

should still be supported if you’ve followed the steps in the migration guide, so if you’re seeing an error that’s a bug. Can you please create an issue on https://github.com/meltano/meltano with steps to reproduce to get that

Extractor failed: Unrecognized replication_method None

error, so that we can look into it further? Including (part of) your

meltano.yml

would be helpful.

@juan_luis_cano_rodriguez did you upgrade from 1.105.0?

thanks @douwe_maan and @edgar_ramirez_mondragon! yes, I saw that supposedly the warnings were harmless, but the cached

discovery.yml

I have in my system is missing some blocks I want, hence the need to upgrade. I'm looking into the issue you sent @edgar_ramirez_mondragon