Skip to content

feat(console): add HubSpot (Jitsu version) source to catalog (JITSU-82)#1376

Open
vklimontovich wants to merge 1 commit into
newjitsufrom
vladimir/jitsu-82-hubspot-fork-catalog
Open

feat(console): add HubSpot (Jitsu version) source to catalog (JITSU-82)#1376
vklimontovich wants to merge 1 commit into
newjitsufrom
vladimir/jitsu-82-hubspot-fork-catalog

Conversation

@vklimontovich

Copy link
Copy Markdown
Contributor

Registers the forked HubSpot connector (jitsucom/source-hubspot) in the source catalog so users can
select HubSpot (Jitsu version) — the fork adds deletion capture in incremental sync (archived
records emitted as _ab_cdc_deleted_at tombstones), which upstream airbyte/source-hubspot can't do.

Adds a JitsuHubspotSource entry and registers it in jitsuSources. Versions resolve live from Docker
Hub, so they appear once the image is published.

Depends on / cross-ref

  • Connector fork PR: jitsucom/source-connectors#1 — must merge and publish the
    jitsucom/source-hubspot image before this is useful.
  • Linear: JITSU-82.

Follow-up (not in this PR)

Migrate the existing "HubSpot Rex" sync config from airbyte/source-hubspot to jitsucom/source-hubspot
(DB update) once the image is live.

🤖 Generated with Claude Code

Register jitsucom/source-hubspot in jitsuSources so the forked HubSpot
connector (with CRM deletion capture) is selectable. Versions resolve from
Docker Hub once the image is published.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017YKm5MHND5s8hpWbVw8VoH

@jitsu-code-review jitsu-code-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed the source-catalog change for jitsucom/source-hubspot and traced how its metadata flows through source listing and version resolution. I found one correctness issue noted inline around MIT-license handling.

packageType: "airbyte",
meta: {
name: "HubSpot (Jitsu version)",
license: "ELv2",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This source is marked ELv2, but /api/sources/versions currently sets isMit = true for any package present in jitsuSources (pages/api/sources/versions.ts, else if (jitsuSources[packageId]) { isMit = true; }). Adding an ELv2 entry here makes that MIT flag incorrect, which can leak non-MIT versions into MIT-compliant filtering paths. Could we derive isMit from jitsuSources[packageId].meta.license (or mitVersions) instead of hard-coding all Jitsu sources as MIT?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant