Skip to content

fix(source-amazon-seller-partner): remove deprecated GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE stream#74065

Draft
Danylo Jablonski (DanyloGL) wants to merge 2 commits intomasterfrom
devin/1772116275-remove-settlement-report-deprecation
Draft

fix(source-amazon-seller-partner): remove deprecated GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE stream#74065
Danylo Jablonski (DanyloGL) wants to merge 2 commits intomasterfrom
devin/1772116275-remove-settlement-report-deprecation

Conversation

@DanyloGL
Copy link
Collaborator

@DanyloGL Danylo Jablonski (DanyloGL) commented Feb 26, 2026

What

Removes the GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE stream from the Amazon Seller Partner source connector ahead of its Amazon SP-API removal date of March 25, 2026.

Amazon deprecated this report type on March 17, 2025 and will permanently remove it on March 25, 2026. See: SP-API Deprecation Schedule

Resolves: https://github.com/airbytehq/oncall/issues/10367 (settlement reports portion)

How

Pure deletion — removes all references to the settlement report stream:

  • manifest.yaml: Removed stream definition (get_v2_settlement_report_data_flat_file), its parent helper stream (flat_file_settlement_v2_helper), the enum entry in the spec, the $ref in the streams list, and the inline schema (~329 lines removed)
  • components.py: Removed FlatFileSettlementV2ReportsTypeTransformer class
  • unit_tests/test_transform_function.py: Removed associated test and import
  • unit_tests/test_source.py: Updated test_streams_count assertion from 52 → 51
  • metadata.yaml: Version bump 5.4.1 → 6.0.0 with breakingChanges entry scoped to this stream, upgrade deadline set to 2026-03-25
  • Test fixtures: Removed stream from acceptance-test-config.yml, configured_catalog_incremental.json, and future_state.json

Follows the same pattern as the v5.0.0 FBA SNS removal.

Review guide

  1. metadata.yaml — Verify the breaking change entry and upgrade deadline are correct
  2. manifest.yaml — Confirm no dangling references remain to settlement or flat_file_settlement_v2_helper
  3. components.py — Confirm FlatFileSettlementV2ReportsTypeTransformer is not referenced by any other stream
  4. Note: ERD files (erd/source.dbml, erd/discovered_catalog.json, erd/estimated_relationships.json) still reference this stream — these are auto-generated and expected to be regenerated separately

User Impact

  • Users syncing the GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE stream will see it removed after upgrading to v6.0.0
  • The upgrade deadline (March 25, 2026) matches Amazon's hard removal date — the stream would fail on that date regardless
  • No impact to users who do not use this stream (scoped breaking change)

Can this PR be safely reverted and rolled back?

  • YES 💚

Link to Devin run: https://app.devin.ai/sessions/198956df19494e578b837c4fe81746aa
Requested by: Danylo Jablonski (@DanyloGL)

…T_REPORT_DATA_FLAT_FILE stream

Remove the settlement report stream (GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE) per Amazon SP-API deprecation.
The report type is deprecated March 17, 2025 and will be removed March 25, 2026.

See: https://developer-docs.amazon.com/sp-api/docs/sp-api-deprecations
Resolves: airbytehq/oncall#10367
Co-Authored-By: Danylo Jablonski <daniel.i.jablonski@globallogic.com>
@devin-ai-integration
Copy link
Contributor

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@github-actions
Copy link
Contributor

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

💡 Show Tips and Tricks

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

  • 🛠️ Quick Fixes
    • /format-fix - Fixes most formatting issues.
    • /bump-version - Bumps connector versions, scraping changelog description from the PR title.
  • ❇️ AI Testing and Review (internal link: AI-SDLC Docs):
    • /ai-prove-fix - Runs prerelease readiness checks, including testing against customer connections.
    • /ai-canary-prerelease - Rolls out prerelease to 5-10 connections for canary testing.
    • /ai-review - AI-powered PR review for connector safety and quality gates.
  • 🚀 Connector Releases:
    • /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
    • /bump-progressive-rollout-version - Bumps connector version with an RC suffix (2.16.10-rc.1) for progressive rollouts (enableProgressiveRollout: true).
      • Example: /bump-progressive-rollout-version changelog="Add new feature for progressive rollout"
  • ☕️ JVM connectors:
    • /update-connector-cdk-version connector=<CONNECTOR_NAME> - Updates the specified connector to the latest CDK version.
      Example: /update-connector-cdk-version connector=destination-bigquery
    • /bump-bulk-cdk-version bump=patch changelog='foo' - Bump the Bulk CDK's version. bump can be major/minor/patch.
  • 🐍 Python connectors:
    • /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
    • /poe source example lock - Alias for /poe connector source-example lock.
    • /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
    • /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.
  • ⚙️ Admin commands:
    • /force-merge reason="<REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.
      Example: /force-merge reason="CI is flaky, tests pass locally"
📚 Show Repo Guidance

Helpful Resources

📝 Edit this welcome message.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 26, 2026

source-amazon-seller-partner Connector Test Results

485 tests   482 ✅  17m 37s ⏱️
  2 suites    3 💤
  2 files      0 ❌

Results for commit 5a278d1.

♻️ This comment has been updated with latest results.

…n after settlement report removal

Co-Authored-By: Danylo Jablonski <daniel.i.jablonski@globallogic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants