✨Source Retently: Migrate Python CDK to Low-code CDK

[avirajsingh7]

What

Migrating Source retently to Low-Code CDK
Closes #28118

How

Developed using (Configuration Based Source) low-code CDK

Recommended reading order

1. manifest.yaml
2. schemas/*

Test

Acceptance Test

🚨 User Impact 🚨

No breaking changes, migration to low-code

Migrate Connector : Source retently

• Community Member? Grant Edit Access to Maintainers instructions
• Secrets in the Connector's Spec
• Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run ./gradlew :airbyte-integrations:connectors::integrationTest.
• Code Reviews Completed
  • Documentation Updated
  • Connector's README.md
  • Connector's bootstrap.md
  • docs/integrations//.md (including changelog. See changelog example)
  • docs/integrations/README.md
  • airbyte-integrations/builds.md
• PR Name follows PR Naming Conventions

[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.

[sajarin]

Thanks for the contribution! Can you resolve the merge conflict @avirajsingh7?

[avirajsingh7]

@sajarin sorry of that, resolved now

[sajarin]

looks good, some minor comments after running tests locally

[avirajsingh7]

@sajarin can you check now?

[sajarin]

Thanks for the PR @avirajsingh7! This has been merged and tested in #29164. The reason why I wasn't able to merge this PR was because I needed to push some changes and run them against our CI but couldn't push to your branch since I didn't have branch permissions. Nevertheless, I forked your changes and tested in the PR aforementioned.

I'm closing this PR but this should still count for the hackathon of course. fyi @RealChrisSean

[avirajsingh7]

thanks @sajarin