-
Notifications
You must be signed in to change notification settings - Fork 31
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
Release/3.0.0 #395
Merged
Merged
Release/3.0.0 #395
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
6ffab12
to
2de0024
Compare
414a52d
to
050a8e7
Compare
This add running spec for iglu routes so we document the bahaviour of that widely used endpoint.
Previously, idleTimeout has been hardcoded, maxConnections hasn't been configured. Now, these parameters are set within `networking` section and used throughout http4s backends.
Adds the ability to configure collector's root (GET `/`) response. If `rootResponse.enabled = true` when `/` is requested a static, configured response is returned. With status code equal to `rootResponse.statusCode`, http headers of `rootResponse.headers` and body of `rootResponse.body`
crossdomain.xml provides cross-domain functionality to Adobe Flash/Flex, but these days Adobe Acrobat. The functionality is required when a tracker request is embedded in a pdf. In this case, when user opens up a PDF file with a script hosted on domain a.com, the script will fetch the crossdomain.xml policy from domain b.com to check whether the endpoint can be accessed and that's used by Adobe to conditionally issue requests.
This is a server-side option to disable tracking once events are received from a tracker. These requests are not sank and instead are silently discarded. Trackers also enable a similar mechanism[1] that will not pass events to the collector. This is likely a better approach, but having it in the collector is another prevention mechanism. 1 - https://docs.snowplow.io/docs/collecting-data/collecting-from-own-applications/javascript-trackers/web-tracker/tracker-setup/initialization-options/#respecting-do-not-track
Previously we've moved on to using a full name which was incompatible with the old format. Now the name uses the expected short name (`ssc-$VERSION-$SINK`) format.
We no longer implement specific warmup logic.
Since introducing a new license we need to explicitly check if the user has accepted the terms. Therefore a new flag is added. By default it is set to false but can be overrided by either: - setting `license.accept = true` in the config file - setting `env ACCEPT_LIMITED_USE_LICENSE=true` - appending `-Dlicense.accept=true`
AlexBenny
approved these changes
Jan 8, 2024
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.
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.
final terraform PR: https://github.com/snowplow-devops/terraform-modules/pull/6850