If I have a plugin that inherits from another I should be able to override the metadata extra in the inherited plugin configuration, right? I have a plugin set up that inherits from another (tap-mysql, in case it matters) and while the

select

list from the inherited plugin is correctly used the

metadata

settings appear to be completed ignored... to get those to work I have to define the metadata in the base plugin, which kinda defeats the point.

I'd think it'd work, I haven't done this with the metadata key myself. Maybe submit an issue with a repo example?

Thanks @visch. Any suggestions for a simple tap that has metadata extras? I can provide a config that demonstrates the problem using the MySQL tap but that requires more setup effort than I like a bug report to require...

tap-postgres

?

podman run -e POSTGRES_PASSWORD=postgres -p 5432:5432 -h postgres -v /home/visch/git/postgres:/custom/mount -d postgres

You should be able to do it with any tap theoretically,

tap-smoke-test

then do --dump=catalog with / without metadata extras and then the tap doesn't even need to run

Thanks! I did not know about tap-smoke-test... that'll definitely be useful for this and other things too, I'm sure