feat(code): remove public api token requirement for segment profiles destination #5329
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
**Before this PR:** - The documentation for the Segment Profiles Destination included steps to create & use a Public API Token **After this PR:** - This requirement is no longer required as [STRATCONN-2388](https://segment.atlassian.net/browse/STRATCONN-2388) removed the need for a Public API Token **Reason that prompted this change:** [Slack Thread in #questions-reverse-etl](https://twilio.slack.com/archives/C03NK2Y2GTC/p1694470953510579)
pwseg
approved these changes
Sep 12, 2023
pwseg
added
the
content-update
|
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
Before this PR:
After this PR:
Reason that prompted this change:
Slack Thread in #questions-reverse-etl
Merge timing