Hi team! Starting today, we've been receiving some Singer SDK deprecation warnings on the postgres tap, which looks due to this PR which was merged today. Most of the warnings are about "passing file paths" to catalog, state, as a list of configs, etc. • I wonder it it means tap-postgres would need to be updated? • I'm not able to see file paths in our meltano.yml. Thanks!

- name: prod

config:

plugins:

extractors:

- name: tap-postgres-mobilemoney-to-dw

config:

host: ${POSTGRES_PROD_MOBILEMONEY_HOST}

database: ${POSTGRES_PROD_MOBILEMONEY_DATABASE}

port: ${POSTGRES_PROD_MOBILEMONEY_PORT}

user: ${POSTGRES_PROD_MOBILEMONEY_USER}

password: ${POSTGRES_PROD_MOBILEMONEY_PASS}

default_replication_method: INCREMENTAL

....

plugins:

extractors:

- name: tap-postgres-mobilemoney-to-dw

inherit_from: tap-postgres

variant: meltanolabs

pip_url: git+<https://github.com/MeltanoLabs/tap-postgres.git>

config:

stream_maps: ###### RENAME TABLES AND CAST TYPES HERE

public-payment_requests_paymentrequest:

__alias__: raw_mobilemoney_paymentrequest

filter:

schemas: public

metadata:      ###### DEFINE HOW TO REPLICATE HERE

public-payment_requests_paymentrequest:

replication-method: INCREMENTAL

replication-key: date_created

select:

- public-payment_requests_paymentrequest.*

Hey @Marcelo Mallmann 👋 Thanks for letting me know. The warnings are being logged so that's good! I plan to address this upstream in the Singer SDK so you shouldn't need to worry about those warnings in particular.

Thank you Edgar