-
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
airbyte-ci: do not eagerly fetch connector secrets #38615
airbyte-ci: do not eagerly fetch connector secrets #38615
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @alafanechere and the rest of your teammates on Graphite |
8ec5f67
to
8133703
Compare
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.
LGTM!
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.
Kudos to the quick resolution
Im not the biggest fan of moving this to the context store (simply because if we keep this pattern up then context.py becomes a very very large file)
But! Lets get a fix out.
Approved
8133703
to
22d6e0b
Compare
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
What
#38322 introduces an edge case bug when
airbyte-ci connectors test
is run with--skip-step
or--only-step
:Even if some test suites are skipped the existing logic tried to fetch the secrets from the secret stores.
It breaks community CI and other workflow which only run a portion of the full test pipeline.
Solution
Fetch secerts according to the
run_step_options
.A lot of secret related logic moved to the ConnectorContext class as it's where these options are exposed.