🐛 Source Stripe: Adjusted Setup Attempts and extended Checkout Sessions stream schemas, fix expected records

[bazarnov]

What

Based on this test:

Need to update expected records, fix the checkout_sessions, setup_attempts stream schemas

How

• adjusted the [properties][payment_method][customer] in setup_attempts stream, according to the Stripe Docs - payment methods object
• extended the setup_attempts stream schema with client_secret (link), ui_mode (link) fields, which were unexpected while running CAT
• updated expected records.jsonl

🚨 User Impact 🚨

This is the semi-breaking change, touching only the setup attempts stream, which is not in the list of the suggested streams. Consider this as a minor update.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 19, 2023 10:27am

[github-actions]

Before Merging a Connector Pull Request

Wow! 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:

• PR name follows PR naming conventions
• Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
• Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
• You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
• Secrets in the connector's spec are annotated with airbyte_secret
• All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
• Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
• Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
• If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

1. Check for hidden checklists in your PR description

2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.

[airbyte-oss-build-runner]

source-stripe test report (commit 6739191d7e) - ✅

⏲️ Total pipeline duration: 09mn14s

Step	Result
Build source-stripe docker image for platform(s) linux/x86_64	✅
Unit tests	✅
Acceptance tests	✅
Code format checks	✅
Validate metadata for source-stripe	✅
Connector version semver check	✅
Connector version increment check	✅
QA checks	✅

🔗 View the logs here

☁️ View runs for commit in Dagger Cloud

Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command

airbyte-ci connectors --name=source-stripe test

[girarda]

! Out of curiosity, do we know why our seed data disappeared?

[bazarnov]

@Diana-Vait Maybe you know the answer for the question? @girarda I didn't find the reason.

[Diana-Vait]

@girarda I also don't have this information. My only guess is that our previous subscription was overdue, but I'm not shure.