Archive unpopular / unsupported destinations

[evantahler]

More information in the doc. Depends on #35355 and https://github.com/airbytehq/airbyte-platform-internal/pull/11405. Don't merge this until both of these are merged in.

This PR Should not be merged until all comments in the linked doc are resolved.

[vercel]

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

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	⬜️ Ignored (Inspect)	Visit Preview		Feb 28, 2024 1:07am

[erohmensing]

Blocking until we are sure that archived will not break the platform (comment) if an archived connector makes its way into a registry for any reason.

[evantahler]

https://github.com/airbytehq/airbyte-platform-internal/pull/11405 is merged, so this should be ready to go!

[erohmensing]

Approving as PRs resolving the potential breaking of the platform are merged.

Thanks for creating a PR to handle hiding the archived connectors from the UI if they make it into a catalog. Please go ahead and remove them from the LaunchDarkly flag after that is merged!

There is some stuff we could do if we really want to do this right, in that we probably would want to make cloud and oss both aware that all these connectors are archived, so that if a user is using a connector that is now archived, they can see that in their UI. That would however involve releasing all the connectors (potentially new versions since they last hit cloud), cutting an OSS release so that OSS users have that info too. That's probably not ideal, and what we talked about re: one large catalog with all the info about which registries a connector is available in and if a connector is archived, would probably better solve this problem. I don't expect you to do this, but wanted to raise it in case we are wondering why we don't see these connectors as archived in the UI.

[evantahler]

/approve-and-merge reason="archiving destinations"

[octavia-approvington]

Approve this