Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Either add a new command or an addition format for structuring data for the Hub #253

Open
MeltyBot opened this issue Oct 22, 2021 · 5 comments
Assignees

Comments

@MeltyBot
Copy link
Contributor

Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/254

Originally created by @tayloramurphy on 2021-10-22 17:58:56


I don't have strong opinions about what would be the best here, but either having an option so that users can output a YAML file for the Hub a la --about --format=hub, or if having a separate command --publish would work.

Goal is to output a YAML file similar to https://gitlab.com/meltano/hub/-/blob/main/_data/taps/3plcentral.yml for a given connector.

Of importance is the need for the variants key and structure so that's it's easy to either add as a variant or submit the whole defition.

  • file would be the tap name with tap-
  • YAML
@MeltyBot
Copy link
Contributor Author

@labelsync-manager labelsync-manager bot added the kind/Feature New feature or request label Jun 23, 2022
@stale
Copy link

stale bot commented Jul 18, 2023

This has been marked as stale because it is unassigned, and has not had recent activity. It will be closed after 21 days if no further activity occurs. If this should never go stale, please add the evergreen label, or request that it be added.

@stale stale bot added the stale label Jul 18, 2023
@edgarrmondragon
Copy link
Collaborator

edgarrmondragon commented Jul 19, 2023

The problem with adding a new command/flag for this (a la #1094) is that then all connectors that want to use this feature have to be updated to the latest SDK.

That's fine if it's a developer of a new connector wants to get it added to the Hub. The connector in that case is probably on the latest SDK, or at least the developer is engaged and we can request that they bump their requirement so they can produce the Hub format.

It's a problem for connectors with an older SDK requirement, whose metadata we'd still want to keep in sync in the Hub.

@stale stale bot removed the stale label Jul 19, 2023
Copy link

stale bot commented Jul 19, 2024

This has been marked as stale because it is unassigned, and has not had recent activity. It will be closed after 21 days if no further activity occurs. If this should never go stale, please add the evergreen label, or request that it be added.

@stale stale bot added the stale label Jul 19, 2024
@edgarrmondragon edgarrmondragon self-assigned this Jul 19, 2024
@edgarrmondragon
Copy link
Collaborator

Now that Meltano has meltano/meltano#7907, it could make sense to let the SDK output in the plugin Hub format.

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

No branches or pull requests

3 participants