feat(recon): get Hyperswitch Order Management data through reporting system for recon

[tsdk02]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

• This PR provides support to fetch Hyperswitch Orders data through the reporting system for recon
• Added support to invoke a new Lambda function that will generate the report and push to an S3 bucket.
• The s3_path is generated, and sent to Recon backend, which will poll the s3_path to get the Hyperswitch data when it is available.

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

Motivation and Context

To enable fetching of Hyperswitch data through the reporting system for recon

How did you test it?

Hit the curl:

curl --location 'http://localhost:8080/analytics/v1/merchant/report/order_management' \
--header 'Accept: */*' \
--header 'Accept-Language: en-US,en;q=0.9' \
--header 'Connection: keep-alive' \
--header 'Content-Type: application/json' \
--header 'Origin: http://localhost:9000' \
--header 'Referer: http://localhost:9000/' \
--header 'Sec-Fetch-Dest: empty' \
--header 'Sec-Fetch-Mode: cors' \
--header 'Sec-Fetch-Site: same-site' \
--header 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36' \
--header 'api-key: test_admin' \
--header 'authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoiNmNkZTA0NzYtMTFlMi00NGE5LTlkMjUtOTA5M2QzNDQwZjhlIiwibWVyY2hhbnRfaWQiOiJtZXJjaGFudF8xNzM1MDQxMjkzIiwicm9sZV9pZCI6Im9yZ19hZG1pbiIsImV4cCI6MTczNjg2ODY5Mywib3JnX2lkIjoib3JnX2pwanI5TkFEWlhqSENNYTU5MmF3IiwicHJvZmlsZV9pZCI6InByb19QRHUydVA3aWNuM2lXY0I3V0VVSSIsInRlbmFudF9pZCI6InB1YmxpYyJ9.cMU1hd2q3e5yb5g48FQazzjrIuR78p1mX25bZjiEo80' \
--header 'sec-ch-ua: "Chromium";v="128", "Not;A=Brand";v="24", "Google Chrome";v="128"' \
--header 'sec-ch-ua-mobile: ?0' \
--header 'sec-ch-ua-platform: "macOS"' \
--data-raw '{
    "timeRange": {
        "startTime": "2025-01-08T13:56:15.243333Z",
        "endTime": "2025-01-09T13:56:15.277Z"
    },
    "emails": [
        "[email protected]"
    ]
}'

You should be able to see a LambdaResponse struct as response, with invocation_status_code, and an s3_path of the following format:

s3_path: "org_jpjr9NADZXjHCMa592aw/merchant_1735041293/order_management/2025-01-08T13:56:15_2025-01-09T13:56:15_1736710717_report.csv"

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed the submitted code
• I added unit tests for my changes where possible

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
crates/router/src/analytics.rs	6% smaller
crates/analytics/src/lambda_utils.rs	0% smaller
crates/analytics/src/lib.rs	0% smaller
crates/api_models/src/analytics.rs	0% smaller
crates/api_models/src/events.rs	0% smaller