I'm trying to add a custom loader with hidden credentials and expecting that when I add these credentials in my dev environment, they would go to

.env

. Instead, they are being written into meltano.yml This is the loader:

- name: pipelinewise-target-s3-csv
    namespace: pipelinewise_target_s3_csv
    pip_url: pipelinewise-target-s3-csv
    executable: target-s3-csv
    settings:
    - name: aws_access_key_id
      kind: hidden
    - name: aws_secret_access_key
      kind: hidden
    - name: aws_session_token
      kind: hidden
    - name: s3_bucket
      kind: string

When I do

meltano config pipelinewise-target-s3-csv set aws_access_key_id MYSECRETACCESSKEY

, that key ends up in

meltano.yml

instead of the

.env

file. Is this a bug or am I missing some config or flag I should be using?

Hi @jose_riego_valenzuela! Can you try with

password

instead of

hidden

?

yes, that worked! thanks a lot

I think

hidden

only makes the UI skip displaying the setting the UI, but

password

actually masks it and treats it like a secret

thanks a lot! that makes sense