Our `select:` list in `meltano.yml` is getting pr...
# troubleshooting
b
Our
select:
list in
meltano.yml
is getting pretty long and making our yml a bit large…is there a way to link the select yml portion to an external page/yml? Something like :
select: extract/tables/select.yml?
or something along those lines? This would also be helpful when wanting to pass different
select
lists depending on what environment we are running
meltano squared has an example irl as well
b
@visch thanks! so if i add the included path for a select yml (
select_production.yml
), how would i make sure
select:
in
meltano.yml
use that file?
Copy code
include_paths:
  - './select_production.yml'
select: ?
v
If you want exactly that maybe look at YAML anchors
I think it's all supported, not sure
b
Ok cool ill look into it, thanks!
a
I don't think we'd be able to pull in a yaml anchor from another page as of now, unfortunately. I think each page is evaluate separately.
b
yeah i just tested and looks like it can't be done
a
But - you could move just that tap into its own file. Perhaps not ideal, but could help to keep the rest of the file easier to read
b
thanks @aaronsteers
Sounds like the select list can't live outside meltano.yml
a
You could even just define each extractor in its own file as a pattern:
Copy code
include_paths:
  - './extractors/*.yml'
Sounds like the select list can't live outside meltano.yml
No - not yet (that I'm aware of). Would welcome a feature request on this though if you would like to see it. 👍
b
Definitely. We finally wrapped up fastsync as well so i will pop in and update what u sent before
And that may work with the extractor pattern. So remove the extractor I'm doing this with from meltano.yml and into it's own yml along with adding included_paths linking to it
Sorry on mobile. Be back up on machine in 5 to speak words gooder
v
Sorry I didn't read closer! 😄 glad you have a way forward
b
hey @aaronsteers i created a dir
extractors
with the new yml,
prod_test.yml
, which i have added to the included paths. Here is how i have it setup in
meltano.yml
now:
Copy code
version: 1
send_anonymous_usage_stats: false
project_id: 0ebb5876-102f-4a42-a66a-f6b317821032
include_paths:
  - extractors/prod_test.yml
plugins:
  extractors:
  - name: pipelinewise-tap-mssql
In the prod_test.yml, i added the pipelinewise-tap-mssql extractor yml, but i am most likley doing this incorrectly. Was trying to find some more documentation to help, but would you mind taking a quick look and seeing where/how this needs to be assigned better? This is what exists in `prod_test.yml`:
Copy code
extractors:
  - name: pipelinewise-tap-mssql
    namespace: pipelinewise_tap_mssql
    pip_url: git+<https://github.com/degreed-data-engineering/pipelinewise-tap-mssql>
    executable: tap-mssql
    capabilities:
    - catalog
    - discover
    - state
    settings:
    - name: string
    - name: integer
    - name: boolean
    - name: date-time
    config:
...
...
... (rest of the config)
If i try to install the extractor after its setup like this, i get
Extractor 'pipelinewise-tap-mssql' is not known to Meltano
(i am installing it with
meltano install extractor pipelinewise-tap-mssql
which typically works when not doing it this way.
@aaronsteers nevermind! i just figured it out
i had to remove
- name: pipelinewise-tap-mssql
completely from
meltano.yml
and add the additional specs in
prod_test.yml
above:
Copy code
version: 1
send_anonymous_usage_stats: false
plugins:
  extractors:
  - name: pipelinewise-tap-mssql
    namespace: pipelinewise_tap_mssql
thanks for the direction to you both! This is going to be huge