Open bgadrian opened 1 month ago
It seems that everytime I update the source token the following behaviours exists
existing connectors fails by looking a _vX (v1, v2..) secrets, which they do not exists in AWS Secrets
I was expecting all connectors to use the same credentials as the source TEST functionality
Connector Name
source-facebook-marketing
Connector Version
3.3.15
What step the error happened?
Configuring a new connector
Relevant information
Install Airbyte 1., OSS, Helm, via abctl with external AWS Secrets enabled and external database Try to setup a new source connector facebook marketing (oauth) Important step: Fill both inputs called ACCESS TOKENS (from auth and the other one) (PS I am not sure why there are 2 of them
Setup source
Internally the secret is created, example:
airbyte_workspace_00000000-0000-0000-0000-000000000000_secret_8bdc4dc5-643e-4f4b-9bed-eeeb788e188e
but somehow the plugin looks for the _v1 suffixairbyte_workspace_00000000-0000-0000-0000-000000000000_secret_8bdc4dc5-643e-4f4b-9bed-eeeb788e188e
Relevant log output
Contribute