Summary
User is unable to test a new connector due to the lack of support for the --use-remote-secrets=false option in recent versions of airbyte-ci. Seeking advice on testing methods.
Question
a second newbie question… After getting through all the rest of the CDK tutorial, I could not test because recent versions of airbyte-ci do not support the option --use-remote-secrets=false … any advice on how to test my new connector?
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
['airbyte-ci', 'testing', 'connector-development', 'remote-secrets']
one thing i would note is that up thru step 5 of the tutorial everything is done in poetry run my-awesome-connector so it is a big leap to airbyte-ci and the containerized environment etc etc.
Under the hood of the innocent looking link to airbyte-ci is a long journey to figure out what “GSM” stands for… and i am more or less stuck in this set of side quests
Okay first of all, thank you for the catch, we need to update the docs once we figure it out.
<@U02UC3T12PJ> would you take the lead here please and advise?
I think the solution is that you need a way to put production secrets in a config file at test runtime for airbyte-ci to be able to pick it up. So if --use-remote-secrets is not an option, let’s document a straightforward way.
one thing i would note is that up thru step 5 of the tutorial everything is done in poetry run my-awesome-connector so it is a big leap to airbyte-ci and the containerized environment etc etc.
Under the hood of the innocent looking link to airbyte-ci is a long journey to figure out what “GSM” stands for… and i am more or less stuck in this set of side quests