Update HubSpot docs for new privateAppToken auth #3355
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
markzegarelli
approved these changes
Aug 9, 2022
brennan
approved these changes
Aug 9, 2022
stayseesong
approved these changes
Aug 9, 2022
stayseesong
added
the
content-update
|
Thanks for approving @markzegarelli @stayseesong! Can we merge this in so it is deployed in tomorrow's release? |
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
We must update how customers authenticate with HubSpot due to them deprecating new API key generation. We are rolling out support for this tomorrow morning (Wed Aug 10) and need to update our docs accordingly. We also updated settings descriptions so would need a
make catalogrun. It's fine if we need to wait until Thurs Aug 11 to go out if we don't want to do a separate deploy.Merge timing
Related issues (optional)
JIRA: https://segment.atlassian.net/browse/HGI-29