Archived connectors are not removed from the platform

[girarda]

We recently archived source-google-analytics-v4. The connector is not in the registry anymore, but it is still possible to create a new actor with that definition

Slack thread for context

[natikgadzhi]

Oh this is interesting. I've just looked up source-punk-api that @btkcodedev archived. It still shows up in the Marketplace. What's even more fun, up to date pipeline applied to it and updated it's deps, and republished a new version: #40972.

The metadata for punk api clearly says supportLevel: archived, and registries.cloud.enabled: false.

@evantahler when you worked on archiving, any last steps that we should make on the platform for connectors to be cleaned up from being available?

[natikgadzhi]

Oh, @girarda here's the guide to hiding connectors in the app: https://www.notion.so/Hiding-or-removing-a-connector-from-Cloud-0839d6c26445415d8aab5643a84db75e?pvs=4#a7a5570a1dcf4b03904e29a368a622e7 — I think we didn't do the "tombstone" part.

I wonder what a good process for this looks like. @malikdiarra should we reach out to Compose folks on Slack, or do that ourselves? If it's just changing a column, Python / Marketplace can do it, but it would probably be good to automate so we don't forget?

Should @airbytehq/dev-tooling look into adding that as a step of archiving pipeline?

[girarda]

@natikgadzhi the solution is to follow the 2-step process describe in notion. The issue I ran into is that the platform does not ingest the new support status if the connector is removed from the registry at the same time. I'm ok with "following the process" now that the documentation has been updated.

Closing, but sharing thread for additional context