-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
source-faker
to Beta + Fix AllowedHosts Checks
#22117
Conversation
Airbyte Code Coverage
|
https://github.com/airbytehq/airbyte/actions/runs/4049145884/jobs/6965192810 shows the check doing the right thing for a beta connector with no allowedHosts The test no longer fails now that allowedHosts is added back |
source-faker
to Betasource-faker
to Beta + Fix AllowedHosts Checks
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.
/test connector=connectors/source-faker
Build PassedTest summary info:
|
The |
/publish connector=connectors/source-faker
if you have connectors that successfully published but failed definition generation, follow step 4 here |
* beta faker + no allowed hosts * V2.0.1 * fixup python checks * add back allowedHosts * simplify * simplify releaseStage * bump expected records * More mock logger methods * auto-bump connector version --------- Co-authored-by: Octavia Squidington III <[email protected]>
@YowanR no action needed - just calling out that I moved |
This PR tests that the allowedHosts checks are working properly. They weren't due to some underlying changes in the python utils...
On a happier note, it looks like Faker is meeting the GA criteria! We shouldn't skip Beta, so let's go there now.