-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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 Snapchat Marketing: remove deprecated auth specification #26358
🐛 Source Snapchat Marketing: remove deprecated auth specification #26358
Conversation
…ated authSpecification in favour of advancedAuth
Before Merging a Connector Pull RequestWow! What a great pull request you have here! 🎉 To merge this PR, ensure the following has been done/considered for each connector added or updated:
If the checklist is complete, but the CI check is failing,
|
/test connector=connectors/source-square
Build PassedTest summary info:
|
/test connector=connectors/source-snapchat-marketing
Build PassedTest summary info:
|
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.
Nice!
…keting-source-square-remove-deprecated-auth-specification
…keting-source-square-remove-deprecated-auth-specification
Removed Source Square from this PR to unblock it as Source Snapchat Marketing is blocked by invalid UI creds |
"rootObject": [], | ||
"oauthFlowInitParameters": [["client_id"], ["client_secret"]], | ||
"oauthFlowOutputParameters": [["refresh_token"]] | ||
"advanced_auth": { |
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.
I see the same fields are defined by this spec but differently. Is this a breaking change for the user? If so, do we have a plan for migrating the value of these field? This connector is GA so we should make sure the impact is minimal
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.
@maxi297 no, this is not a breaking change. Nothing changes for the user. It's just another way to describe oauth flow for the server. Anyway, the task is on hold for now because we're currently not able to log in via Snapchat UI :(
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.
as soon as we have access to our account - I'll be able to confirm everything works as expected via manual testing on localhost
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.
Conditional approval given that we have ensured that refresh_token, client_id and client_secret are passed to the new auth spec (see this)
…keting-source-square-remove-deprecated-auth-specification
What
Remove deprecated
authSpecification
from connector spec in favour ofadvancedAuth
#26246
How
Replace
authSpecification
withadvancedAuth