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
fix(lemnisk): add rudder message identifier flag #1198
Merged
MoumitaM
merged 10 commits into
rudderlabs:production-staging
from
praveendsviz:lemnisk-update-rudderstack-flag
Jul 21, 2023
Merged
fix(lemnisk): add rudder message identifier flag #1198
MoumitaM
merged 10 commits into
rudderlabs:production-staging
from
praveendsviz:lemnisk-update-rudderstack-flag
Jul 21, 2023
Conversation
This file contains 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
…s natively on the same web page of customers
praveendsviz
requested review from
ItsSudip,
shrouti1507 and
sandeepdsvs
as code owners
July 5, 2023 17:58
shrouti1507
previously requested changes
Jul 10, 2023
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.
Need to update the test cases
1 task
koladilip
reviewed
Jul 13, 2023
koladilip
approved these changes
Jul 15, 2023
Hi @praveendsviz, Can you please sign the CLA so that we can go ahead with your changes? |
MoumitaM
changed the title
Adding a flag to differentiate calls coming from Rudderstack vs native calls
fix(lemnisk): add rudder message identifier flag to differentiate calls coming from Rudderstack vs native calls
Jul 21, 2023
MoumitaM
changed the title
fix(lemnisk): add rudder message identifier flag to differentiate calls coming from Rudderstack vs native calls
fix(lemnisk): add rudder message identifier flag to differentiate calls coming from rudderstack vs native calls
Jul 21, 2023
MoumitaM
changed the title
fix(lemnisk): add rudder message identifier flag to differentiate calls coming from rudderstack vs native calls
fix(lemnisk): add rudder message identifier flag
Jul 21, 2023
MoumitaM
merged commit Jul 21, 2023
37697f1
into
rudderlabs:production-staging
9 of 12 checks passed
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.
PR Description
There are customers who have rudderstack based implementation of Lemnisk and native implementation of Lemnisk. We are adding a flag to understand the rudderstack based calls.
Notion ticket
Ticket link
Screenshots
Not a UI change
Security