-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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 Facebook Pages: bump FB API version #7128
Conversation
/test connector=connectors/source-facebook-pages
|
/test connector=connectors/source-facebook-pages
|
@@ -122,7 +122,6 @@ | |||
"category_list", | |||
"checkins", | |||
"company_overview", | |||
"connected_instagram_account", | |||
"connected_page_backed_instagram_account", |
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.
We've removed these fields because updated API requires new permissions to access them.
Should we ask users to re-generate their tokens instead? Or removing these fields is ok?
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.
shouldnt we update scopes for oauth?
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.
- We should ask users to regenerate their token. For OSS users this should be pretty straightforward, and since this isn't yet on Cloud then there are no tokens to regenerate. But we have to be super clear about the action required from users in the changelog, because the changelog will be the source of truth for users
- We should update oauth scopes accordingly
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.
Seems like in addition to updating permissions and regenerating the token user needs to create and connect an Instagram business account, as well as accept an additional user agreement. What should we do in this case?
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.
ooh crap. Ok let's remove this then. Not all pages will have a connected instagram profiel.
/test connector=connectors/source-facebook-pages
|
/publish connector=connectors/source-facebook-pages
|
* Upd FB API version * Upd changelog * Exclude fields with extra permissions required
What
Update facebook api version to v12.0
Pre-merge Checklist
Expand the relevant checklist and delete the others.
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampleAirbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing./publish
command described here