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

fix: Only set incoming user agent if not already present #1366

Merged
merged 1 commit into from
Oct 7, 2024

Conversation

MikeGoldsmith
Copy link
Contributor

Which problem is this PR solving?

Following up to the following PR, we should only set the incoming user agent if the key does not already exist. This is useful in certain scenarios when two Refinery's are connected together.

Short description of the changes

  • Only set incoming user agent meta field if the event doesn't already have a value for it
  • Add unit test to verify behaviour
  • Update existing tests to set custom user-agent and verify it's set correctly

@MikeGoldsmith MikeGoldsmith added the type: bug Something isn't working label Oct 7, 2024
@MikeGoldsmith MikeGoldsmith self-assigned this Oct 7, 2024
@MikeGoldsmith MikeGoldsmith requested a review from a team as a code owner October 7, 2024 12:27
@MikeGoldsmith MikeGoldsmith merged commit 42cbc71 into main Oct 7, 2024
6 checks passed
@MikeGoldsmith MikeGoldsmith deleted the mike/incoming-user-agent-dup branch October 7, 2024 15:40
MikeGoldsmith added a commit that referenced this pull request Oct 7, 2024
## Which problem is this PR solving?

Following up to the following PR, we should only set the incoming user
agent if the key does not already exist. This is useful in certain
scenarios when two Refinery's are connected together.

- #1358

## Short description of the changes
- Only set incoming user agent meta field if the event doesn't already
have a value for it
- Add unit test to verify behaviour
- Update existing tests to set custom user-agent and verify it's set
correctly
# Conflicts:
#	app/app_test.go
#	route/route_test.go
TylerHelmuth pushed a commit that referenced this pull request Oct 16, 2024
Following up to the following PR, we should only set the incoming user
agent if the key does not already exist. This is useful in certain
scenarios when two Refinery's are connected together.

- #1358

- Only set incoming user agent meta field if the event doesn't already
have a value for it
- Add unit test to verify behaviour
- Update existing tests to set custom user-agent and verify it's set
correctly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants