what is the added benefit here, i’m a bit lost on this

Have you used meltano much? Give it a try with a use case or two like a tap to target. It'll be easier to understand I think. Generally why you'd include

superset

inside meltano is it makes it easier to not have to push everything to prod to do testing. Meltano knows the config information for your database because you're already pushing data to the data

superset

is probably pulling from and you can reuse some of that configuration information. On top of

config

information you can use

environments

to define things like

dev

uat

prod

environments that all have their own configuration options. Allowing you to do something like

meltano --environment=dev run tap-google target-postgres superset:up

and you could spin up your entire pipeline end to end on your local machine, or maybe you could do ``meltano --environment=uat run tap-google target-postgres superset:up` and you'd run with your development credentials instead of deploying directly to prod. Might be useful where you want to review a pull request from someone else as your CI tool could automatically pull the data in and spin up superset without having to maintain that configuration somewhere else. Sometimes it's very valuable for what you're doing sometimes not, but the ability to add environments down the road makes it pretty nice. The other value add is someone is not familiar with an app, like superset (myself) can spin up superset without having to configure much of anything

oh thank you, noted