chore: enable labels for api calls - 2 #3479
Merged
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
|
Test report for this run is available at: https://test-integrations-dev.s3.amazonaws.com/integrations-test-reports/rudder-transformer/3479/test-report.html |
added 3 commits
June 19, 2024 15:23
- canny - clickup - custify - freshmarketer - freshsales - wootric
- monday - profitwell - sendgrid - sendinblue
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## chore.labels-int-api #3479 +/- ##
=====================================================
Coverage 88.07% 88.07%
=====================================================
Files 577 577
Lines 31216 31231 +15
Branches 7445 7446 +1
=====================================================
+ Hits 27492 27507 +15
+ Misses 3414 3386 -28
- Partials 310 338 +28 ☔ View full report in Codecov by Sentry. |
….labels-int-api-1
* chore: enable labels for api calls - 3 * chore: propagate metadata for user destination * chore: propagate metadata in braze * chore: propagate metadata for api calls in hubspot * chore: propagate metadata for labels in api calls for - pardot - rakuten - snapchat_custom_audience - the_trade_desk - yahoo_dsp * chore: propagate metadata in zendesk Signed-off-by: Sai Sankeerth <sanpj2292@github.com> * chore: propagate metadata in gainsight --------- Signed-off-by: Sai Sankeerth <sanpj2292@github.com> Co-authored-by: Sai Sankeerth <sanpj2292@github.com>
….labels-int-api-1
….labels-int-api-1
ItsSudip
reviewed
Jun 21, 2024
Co-authored-by: Sudip Paul <67197965+ItsSudip@users.noreply.github.com>
yashasvibajpai
approved these changes
Jun 26, 2024
|
sanpj2292
added a commit
that referenced
this pull request
Jul 24, 2024
* chore: enable labels for api calls * chore: propagate metadata to api call fn in intercom dest * chore: metadata propagation in mautic & optimizely_fullstack Signed-off-by: Sai Sankeerth <sanpj2292@github.com> * chore: metadata propagation in active_campaign Signed-off-by: Sai Sankeerth <sanpj2292@github.com> * chore: metadata propagation in delighted & klaviyo Signed-off-by: Sai Sankeerth <sanpj2292@github.com> * chore: add method doc to getRelativePathFromURL * chore: add test-cases to test firing of stats based on metadata * chore: enable labels for api calls - 2 (#3479) * chore: enable labels for api call - 2 * chore: propagate metadata in following destinations - canny - clickup - custify - freshmarketer - freshsales - wootric * chore: propagate metadata for below destinations - monday - profitwell - sendgrid - sendinblue * chore: fix sfmc transformation test * chore: enable labels for api calls - 3 (#3483) * chore: enable labels for api calls - 3 * chore: propagate metadata for user destination * chore: propagate metadata in braze * chore: propagate metadata for api calls in hubspot * chore: propagate metadata for labels in api calls for - pardot - rakuten - snapchat_custom_audience - the_trade_desk - yahoo_dsp * chore: propagate metadata in zendesk Signed-off-by: Sai Sankeerth <sanpj2292@github.com> * chore: propagate metadata in gainsight --------- Signed-off-by: Sai Sankeerth <sanpj2292@github.com> Co-authored-by: Sai Sankeerth <sanpj2292@github.com> * chore: update canny transformation to include await keyword Co-authored-by: Sudip Paul <67197965+ItsSudip@users.noreply.github.com> * chore: add async for canny destination - fix eslint error --------- Signed-off-by: Sai Sankeerth <sanpj2292@github.com> Co-authored-by: Sai Sankeerth <sanpj2292@github.com> Co-authored-by: Sudip Paul <67197965+ItsSudip@users.noreply.github.com> * chore: remove duplicate metadata key in statTags obj klaviyo Signed-off-by: Sai Sankeerth <sanpj2292@github.com> --------- Signed-off-by: Sai Sankeerth <sanpj2292@github.com> Co-authored-by: Sai Sankeerth <sanpj2292@github.com> Co-authored-by: Sudip Paul <67197965+ItsSudip@users.noreply.github.com>
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.
What are the changes introduced in this PR?
Metadata has been propagated for intermediate API calls(to obtain extra metadata in metrics) for below destinations have been added
What is the related Linear task?
Resolves INT-2152
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
Any changes to existing capabilities/behaviour, mention the reason & what are the changes ?
N/A
Any new dependencies introduced with this change?
N/A
Any new generic utility introduced or modified. Please explain the changes.
N/A
Any technical or performance related pointers to consider with the change?
N/A
@coderabbitai review
Developer checklist
My code follows the style guidelines of this project
No breaking changes are being introduced.
All related docs linked with the PR?
All changes manually tested?
Any documentation changes needed with this change?
Is the PR limited to 10 file changes?
Is the PR limited to one linear task?
Are relevant unit and component test-cases added in new readability format?
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.