nehil_jain
07/05/2020, 3:43 PMtap-sourcename then will a correct .env file look like
export SOURCENAME_CONFIGKEY1=value
export SOURCENAME_CONFIGKEY2=value
export SOURCENAME_CONFIGKEY3=value
If the above is true then how does setting PG_URL for target-postgres work, shouldnt it be POSTGRES_PG_URL?
An idea, @douwe_maan we should have a working meltano example repo which can be a starter repo for people to start building their project from.douwe_maan
07/05/2020, 8:22 PMmeltano config <plugin> list to list the available variable names. :)
By default the <namespace>_<name> format is used, but that can be overridden on a per-plugin-per-setting basis to match existing conventions, like in the case of PG_. See the env key under https://meltano.com/docs/contributor-guide.html#changing-discovery-yml.
A working Meltano example repo does exist, in the sequence of code sample statements on the homepage :-) This “project” is verified to work through the homepage_code_sample CI job: https://gitlab.com/meltano/meltano/-/jobs/623650780 and a project created from that same sequence of statements (plus some CI sugar) can be found at https://gitlab.com/meltano/demo-project!
I’d rather not provide an actually example project though, since users would spend as much time deleting stuff that doesn’t apply, as they would adding stuff they actually need. The homepage takes the user through the “journey” of building a demo project, and I hope leaves the user having learned a bit more than than they would from seeing a simple starter project :)
Really, “meltano init” should be seen as creating the starter project, since everything after that will be dependent on your specific goals!
Note that the the homepage sample code does not currently cover transformations or Meltano UI in much detail, exactly because those are not yet features polished enough for the novice user to use, and currently more appropriate for power users like yourself who won’t mind the rough edges ;)