Hi, is the result in meltano.yml file consistent with the documentation?

# Values are parsed as JSON, and interpreted as simple strings when invalid

meltano config <plugin> set <name> <json> # JSON that fits in a single word

commands:

meltano config tap-spreadsheets-anywhere set _schema my_entity my_attribute my_key_1 [\"test\"]
meltano config tap-spreadsheets-anywhere set _schema my_entity my_attribute my_key_2 [\"test\", \"test\"]

→ meltano.yml:

plugins:
  extractors:
  - name: tap-spreadsheets-anywhere
    pip_url: git+<https://github.com/ets/tap-spreadsheets-anywhere.git>
    schema:
      my_entity:
        my_attribute:
          my_key_1:
          - test
          my_key_2:
            '["test",': '"test"]'

Hi @jan_fertek! Looks like some shell issue with the quotes/escaping. Can you try instead:

meltano config tap-spreadsheets-anywhere set _schema my_entity my_attribute my_key_2 '["test", "test"]'

@jan_fertek - One additional thing to check is whether

kind

is set correctly for the setting in question. For custom taps/targets, you may need to set these yourself in meltano.yml.

Thanks!

Can you try instead …

Your suggestion (=

'["test", "test"]'

) works,

"[\"test\", \"test\"]"

can be used also. I tried many variants:

(meltano config tap-spreadsheets-anywhere set _schema my_entity my_attribute) my_key_6 "['test', 'test']"
(dtto) my_key_7 '["test", "test"]'
(dtto) my_key_8 "[\"test\", \"test\"]"
(dtto) my_key_9 '[\'test\', \'test\']' # expects input => Ctrl+C

(dtto) my_key_10 ["test", "test"]
(dtto) my_key_11 ['test', 'test']

(dtto) my_key_12 [\"test\", \"test\"]
(dtto) my_key_13 [\'test\', \'test\']

Results in meltano.yml:

my_key_6: '[''test'', ''test'']'
my_key_7:
- test
- test
my_key_8:
- test
- test
my_key_10:
  '[test,': test]
my_key_11:
  '[test,': test]
my_key_12:
  '["test",': '"test"]'
my_key_13:
  '[''test'',': '''test'']'

Variants 7 and 8 are usable for me. To my original question: I was surprised that the first command creates a list in YAML, but the second command does not.

One additional thing to check is whether kind is set correctly for the setting in question.

I am configuring plugin extras (=

_schema

). I thought that

kind

can be used for regular plugin-specific settings only.