Skip to content
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-hubspot-native: use v3 of the owners API #2291

Merged
merged 1 commit into from
Jan 23, 2025
Merged

Conversation

williamhbaker
Copy link
Member

@williamhbaker williamhbaker commented Jan 23, 2025

Description:

The v2 owners API has been deprecated and actually doesn't even work on newer accounts. We need to use the v3 owners API instead of the v2 owners API to prevent issues with newer HubSpot accounts.

The API output is slightly different between the v3 and the v2 API, but since this is a snapshot stream anyway and very low volume for our current use cases, I'm not anticipating that being a huge issue.

We could build in some kind of backward compatibility to make the v2 and v3 output more the same, or have captures that are able to use the v2 API or something like that, but I don't think that is worth the long-term maintenance cost we would take on.

Workflow steps:

(How does one use this feature, and how has it changed)

Documentation links affected:

(list any documentation links that you created, or existing ones that you've identified as needing updates, along with a brief description)

Notes for reviewers:

(anything that might help someone review this PR)


This change is Reviewable

The v2 owners API has been deprecated and actually doesn't even work on newer
accounts. We need to use the v3 owners API instead of the v2 owners API to
prevent issues with newer HubSpot accounts.

The API output is slightly different between the v3 and the v2 API, but since
this is a snapshot stream anyway and very low volume for our current use cases,
I'm not anticipating that being a huge issue.

We could build in some kind of backward compatibility to make the v2 and v3
output more the same, or have captures that are able to use the v2 API or
something like that, but I don't think that is worth the long-term maintenance
cost we would take on.
Copy link
Member

@Alex-Bair Alex-Bair left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks!

@williamhbaker williamhbaker merged commit f60b94e into main Jan 23, 2025
75 of 82 checks passed
@williamhbaker williamhbaker deleted the wb/hsn-v3-owners branch January 23, 2025 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants