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

feat: remove segment.io support, fixes #5365 #5997

Merged
merged 5 commits into from
Mar 24, 2024

Conversation

rfay
Copy link
Member

@rfay rfay commented Mar 20, 2024

The Issue

We stopped actually using Segment.io in v1.22.0 because it's too expensive and we switched to using Amplitude

Now for v1.23, we can just remove that.

Manual Testing Instructions

Manual testing is super-critical here. We need to make absolutely sure that we haven't broken Amplitude

  • With amplitude enabled, take actions and see results in Amplitude

Automated Testing Overview

Related Issue Link(s)

Release/Deployment Notes

@github-actions github-actions bot added dependencies Pull requests that update a dependency file enhancement labels Mar 20, 2024
Copy link

github-actions bot commented Mar 20, 2024

@rfay rfay marked this pull request as ready for review March 21, 2024 02:42
@rfay rfay requested review from a team as code owners March 21, 2024 02:42
@rfay rfay requested a review from stasadev March 21, 2024 02:43
Copy link
Member

@stasadev stasadev left a comment

Choose a reason for hiding this comment

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

I tested this manually and I can see my user events in Amplitude with this PR.

To remove: SegmentKey in Makefile and in .github/workflows/master-build.yml.

I noticed comments for InitAmplitude, should it be done here as well?:

ddev/cmd/ddev/main.go

Lines 14 to 16 in 55053f0

// Initialization is currently done before via init() func somewhere while
// creating the ddevapp. This should be cleaned up.
amplitude.InitAmplitude()

@rfay rfay force-pushed the 20240320_remove_segmentio branch from eb7143f to 4d43aa4 Compare March 22, 2024 17:40
@rfay
Copy link
Member Author

rfay commented Mar 22, 2024

Thanks for the good eye. turned out that the check on ddev config global wasn't valid any more, we do it only on start (and now on ddev version)

On

This should be cleaned up

That was Simon's hope to remove init() usage in the future, which is definitely a valid hope.

Copy link
Member

@stasadev stasadev left a comment

Choose a reason for hiding this comment

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

Noticed one more leftover for SegmentKey in .github/workflows/master-build.yml

@rfay
Copy link
Member Author

rfay commented Mar 22, 2024

Noticed one more leftover for SegmentKey

I guess I got distracted fixing that and adding the warning to ddev version

Turned out that hadn't been working for ages; we changed a long time ago to only check on ddev start but now added the check to ddev version.

@rfay rfay force-pushed the 20240320_remove_segmentio branch from 5c8465a to b058c5e Compare March 24, 2024 16:38
@rfay
Copy link
Member Author

rfay commented Mar 24, 2024

Rebased this and retested, and it seems to be right. I checked go mod tidy and go mod vendor and they seem to be unchanged.

@rfay rfay merged commit 77bbe0f into ddev:master Mar 24, 2024
6 of 9 checks passed
@rfay rfay deleted the 20240320_remove_segmentio branch March 24, 2024 16:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants