feat: onboard new destination the trade desk

[Gauravudia]

What are the changes introduced in this PR?

Resolves INT-1167

• Onboard the new destination: The Trade Desk
• Onboard a destination on transformer proxy, addressing two key issues:
  • Handling error responses in the event of a 200 status code.
  • Resolving an issue caused by the server sorting payload keys, impacting the decryption of the HMAC at the Trade Desk's end. To overcome this challenge, a proxy request has been created, generating the HMAC of the sorted payload JSON keys.
• Used new audience message type: record. This allows the server to send each record individually, with the transformer responsible for efficiently batching the events.
• Onboard destination on router to support new audience message type: record
• Added a utility function, splitItemsBasedOnMaxSizeInBytes, designed to split an items array containing various IDs (TDID, DAID, UID2) based on the maximum base size allowed by Trade Desk (approximately 2.5MB).
• Implemented a utility function, getSignatureHeader, to generate the HMAC of the payload using secret keys (advertiser secret key and provided data secret key).

Please explain the objectives of your changes below

Put down any required details on the broader aspect of your changes. If there are any dependent changes, mandatorily mention them here

1. Server changes to pass destination config in metadata is required for this Integration to work correctly. Without this change transformer will throw configuration error.
2. Adding data provider secret key in transformer env.

Type of change

new feature

Any technical or performance related pointers to consider with the change?

N/A

Any new dependencies introduced with this change?

N/A

Any new generic utility introduced or modified. Please explain the changes.

existing utility: prepareProxyRequest in network.js is modified to return config from request. This config will be later used by calling function proxyRequest in networkHandler.js of Trade Desk

If the PR has changes in more than 10 files, please mention why the changes were not split into multiple PRs.

N/A

If multiple linear tasks are associated with the PR changes, please elaborate on the reason:

N/A

---

Developer checklist

• No breaking changes are being introduced.

• Are all related docs linked with the PR?

• Are all changes manually tested?

• Does this change require any documentation changes?

• Are relevant unit and component test-cases added?

Reviewer checklist

• Is the type of change in the PR title appropriate as per the changes?

• Verified that there are no credentials or confidential data exposed with the changes.

[coderabbitai]

Important

Auto Review Skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository.

To trigger a single review, invoke the @coderabbitai review command.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit's AI:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid.
  • @coderabbitai read the files in the src/scheduler package and generate README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[codecov]

Codecov Report

Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (8bada4b) 87.20% compared to head (b6c58a9) 87.28%.

Files	Patch %	Lines
src/cdk/v2/destinations/the_trade_desk/utils.js	96.72%	2 Missing ⚠️
...c/v0/destinations/the_trade_desk/networkHandler.js	93.54%	2 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #2918      +/-   ##
===========================================
+ Coverage    87.20%   87.28%   +0.07%     
===========================================
  Files          864      872       +8     
  Lines        29373    29500     +127     
  Branches      6854     6865      +11     
===========================================
+ Hits         25616    25749     +133     
+ Misses        3411     3405       -6     
  Partials       346      346              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[koladilip]

so we can merge this directly or we need to deploy this only to exinity? cc: @krishna2020

[krishna2020]

so we can merge this directly or we need to deploy this only to exinity? cc: @krishna2020

Requirement is only for exinity customer. This PR has changes only w.r.t TradeDesk destination - so good to merge too. However exinity should have dedicated transformer deployment for enabling v1 proxy - so deploying this branch also works.

[sonarqubecloud]

Quality Gate passed

The SonarCloud Quality Gate passed, but some issues were introduced.

1 New issue
0 Security Hotspots
94.1% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud