-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
feat: add the pro activation to the tracked environment variables #12902
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
Conversation
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.
Welcome to LocalStack! Thanks for raising your first Pull Request and landing in your contributions. Our team will reach out with any reviews or feedbacks that we have shortly. We recommend joining our Slack Community and share your PR on the #community channel to share your contributions with us. Please make sure you are following our contributing guidelines and our Code of Conduct.
All contributors have signed the CLA ✍️ ✅ |
S3 Image Test Results (AMD64 / ARM64) 2 files 2 suites 8m 59s ⏱️ Results for commit eff12c7. |
I have read the CLA Document and I hereby sign the CLA |
Motivation
Tracking the
ACTIVATE_PRO
will enable us to identify sessions that use the pro image with an invalid token and fall back to the community image.Context:
Some users set an invalid token using the pro image and set the
ACTIVATE_PRO=0
variable.Without this, it appears that someone started a session with an invalid token using the pro image, which is misleading, as they would fall back to the community in this situation.
What changes does this PR make?
Adds
ACTIVATE_PRO
to the list of tracked environment variables that are sent to the analytics backend, so that it's ingested into TinyBird.