I'm working on a custom fork of

target-redshift

to fix an issue. Will contribute upstream if it works. As part of this, I've added a new config setting to the target. I've changed my meltano.yml to:

- name: target-redshift
    variant: ticketswap
    pip_url: git+<https://github.com/coviu/target-redshift.git@region-setting>

I can see that Meltano installed my fork fine, but it won't update the lockfile. I'm not sure how to make it do this... or if this is a problem or not.

Not a problem - the

.lock

file is managed by Meltano and can be updated when there are upstream changes to the plugin definition in the Hub 🙂 You've done the correct thing in overriding the

pip_url

in the

meltano.yml

, and (if you haven't already figured it out) you can supply your new setting definition under `settings`:

- name: target-redshift
    variant: ticketswap
    pip_url: git+<https://github.com/coviu/target-redshift.git@region-setting>
    settings:
    - name: region

https://docs.meltano.com/reference/plugin-definition-syntax#settings Then Meltano will be able to read config for

region

from the

meltano.yml

config:
      region: eu-west-1

or shell environment/`.env`

TARGET_REDSHIFT_REGION=eu-west-1

Thanks for the explanation, @Reuben (Matatika)!