-
Notifications
You must be signed in to change notification settings - Fork 88
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
fix: team schema parent field to object #107
Conversation
Hi @sonac, thanks for your contribution! In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. |
You did it @sonac! Thank you for signing the Singer Contribution License Agreement. |
Hi @cmerrick! We're receiving the same error and this PR would resolve it. Is there any timeline to getting this merged? |
Hi @cmerrick! Chiming in as someone else looking forward to this pull request landing, as we are blocked with the same error that this PR is intended to resolve...
|
Hey @jcw- @ericalouie @sonac thank you for keeping up with and bumping this issue. It's really helpful to see the engagement. The team has been able to validate it and put forth in another PR #149 that will be released in the next version. Going to close this PR in lieu of that one. |
@jcw- @ericalouie @sonac @dmosorast This is released to Prod today |
@KrisPersonal @dmosorast thanks so much! this is now letting me sync those tables - however it does thousands of HTTP calls for "memberships", around 4k in my case (and many calls against team_members), and eventually hits:
We use nested teams - I'm wondering if that's something that might be causing some sort of unexpected behavior... issue added here: #151
|
Description of change
This change related to #94
I've taken it, since we're running into this issue in stitchdata load (which uses tap)
Manual QA steps
At the moment stitch load throws
when a team has non-null parent
Also according to GitHub docs, it is an object: https://docs.github.com/en/rest/reference/teams#list-child-teams
Risks
Minimal, since its only changing type for one field
Rollback steps