-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
🚨🚨🐛Source Amazon Seller Partner: update schema for GET_FBA_STORAGE_FEE_CHARGES_DATA
stream
#35439
Conversation
…HARGES_DATA stream
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
GET_FBA_STORAGE_FEE_CHARGES_DATA
streamGET_FBA_STORAGE_FEE_CHARGES_DATA
stream
Before Merging a Connector Pull RequestWow! What a great pull request you have here! 🎉 To merge this PR, ensure the following has been done/considered for each connector added or updated:
If the checklist is complete, but the CI check is failing,
|
Should this be a breaking change, as this PR can affect OSS users? |
@@ -85,16 +85,16 @@ | |||
"qualifies_for_inventory_discount": { | |||
"type": ["null", "string"] | |||
}, | |||
"storage-utilization-ratio": { | |||
"storage_utilization_ratio": { |
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.
Is it braking change?
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.
I would say yes if there were active users of the stream on cloud (based on this page). Since there are no customers, I decided not to mark this PR as a breaking change, however, based on @tolik0's comment above, this might affect OSS users. I don't know if the same logic of connector upgrade applies to them, so could you please advice if I should consider this as a breaking change?
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.
Yes, let's mark this as braking changes.
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.
Updated, please take a look
GET_FBA_STORAGE_FEE_CHARGES_DATA
streamGET_FBA_STORAGE_FEE_CHARGES_DATA
stream
Users will need to refresh the source schemas and reset these streams after upgrading. | ||
upgradeDeadline: "2024-01-12" | ||
4.0.0: | ||
message: | ||
Stream `GET_FBA_STORAGE_FEE_CHARGES_DATA` now has updated schema, which matches Amazon Seller Partner docs. |
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.
Stream GET_FBA_STORAGE_FEE_CHARGES_DATA
schema has been updated to match Amazon Seller Partner.
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.
Updated
4.0.0: | ||
message: | ||
Stream `GET_FBA_STORAGE_FEE_CHARGES_DATA` now has updated schema, which matches Amazon Seller Partner docs. | ||
Users will need to refresh the source schemas and reset these streams after upgrading. |
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.
Users will need to refresh the source schema and reset this stream after upgrading.
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.
Updated
message: | ||
Stream `GET_FBA_STORAGE_FEE_CHARGES_DATA` now has updated schema, which matches Amazon Seller Partner docs. | ||
Users will need to refresh the source schemas and reset these streams after upgrading. | ||
upgradeDeadline: "2024-03-11" |
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.
Does this autolink to the migration guide?
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.
No. Do you have an example of how this should look like?
|
||
Stream `GET_FBA_STORAGE_FEE_CHARGES_DATA` now has updated schema, which matches Amazon Seller Partner [docs](https://developer-docs.amazon.com/sp-api/docs/fba-inventory-reports-attributes#get_fba_storage_fee_charges_data). | ||
|
||
Users will need to refresh the source schemas and reset these streams after upgrading. |
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.
Users will need to refresh the source schema and reset this stream after upgrading.
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.
Updated
What
Update the schema for the
GET_FBA_STORAGE_FEE_CHARGES_DATA
stream according to the request in certification checklist and Amazon docsRecommended reading order
GET_FBA_STORAGE_FEE_CHARGES_DATA.json
🚨 User Impact 🚨
This is a breaking change as field names in the
GET_FBA_STORAGE_FEE_CHARGES_DATA
stream's schema have been renamedPre-merge Actions
Updating a connector
Community member or Airbyter
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.