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

[avirajsingh7]

What

Migrating Source pipedrive to Low-Code CDK
Closes #29285

How

Developed using (Configuration Based Source) low-code CDK

Recommended reading order

1. manifest.yaml
2. schemas/*

🚨 User Impact 🚨

Are there any breaking changes? What is the end result perceived by the user?
added some new properties in schema as per response from API

Test

Acceptance Test

Migrate Connector : Source Hubplanner

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

[marcosmarxm]

Hello 👋 , right now Airbyte's integration tests are failing for this connector and I'm going to work during the week to fix them. Due a high number of contributions we have a backlog and your contribution will be review next week. We ask to you share the integration test from your side whatever possible and if you don't have credentials to run tests to get in touch with @RealChrisSean as soon as possible. Also some common missing steps contributors does migrating to low code are (and you can double check to make sure you implemented this):

• adding paginator
• update the documentation changelog + metadata file and dockerfile version
• if the connector has start_date parameter you must implement incremental syncs

[marcosmarxm]

@avirajsingh7 can you give me access to your branch to push some changes?

[avirajsingh7]

@marcosmarxm send you a collabrator request

But stiil edit by mentors are allowed you can push to branch

[marcosmarxm]

Thanks @avirajsingh7

[marcosmarxm]

/approve-and-merge reason="expired credentials, small migration and using native components"

[octavia-approvington]

A crack team of mammals has made a decision.