-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Data plane needs gcp secret hydrator and persistence for replication activity #17149
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@xiaohansong this looks good from a code perspective! Did this only come up now because our test syncs that we ran in AWS Dev didn't require secrets?
@pmossman that's right - especially for destination because I always used e2e testing one |
…activity (airbytehq#17149) * use prototype for jwt signature because we need a new one * add comments on why using provider and prototype: * secret hydrator fix for data plane * style fix
…activity (airbytehq#17149) * use prototype for jwt signature because we need a new one * add comments on why using provider and prototype: * secret hydrator fix for data plane * style fix
What
Give GCP Secret hydrator and persistence for data plane workers.