@ricky_renner, @hassan_syyid Sharing back this quick summary back to the channel in a new thread, since this original thread is now quite long and covering multiple topics. As discussed in the thread: 1. Meltano does not support 'settings write-back' by the tap/target - although we do have a ticket open to explore those requirements. 2. Meltano by default will generate a new config file each time the tap and target are invoked, cleaning up those files after execution for security purposes. 3. @ricky_renner has documented here that

tap-quickbooks

does support and/or expect this to handle a rotating

refresh_token

. 4. To my knowledge, we don't (yet) have a way to run meltano

elt

with a self-managed config file. For past use cases, we generally found there was some workaround in the tap itself. So far, just

tap-jira

and

tap-quickbooks

have been identified. I believe

tap-jira

had a workaround so it dropped off the priority. @hassan_syyid mentioned that the

tap-quickbooks

setting called

is_sandbox

may be a workaround but I can't speak to that myself.