meltano
Distinguish Files plugins that are dependencies of other plugins
Migrated from GitLab: https://gitlab.com/meltano/hub/-/issues/262
Originally created by @tayloramurphy on 2022-05-27 21:05:36
From https://gitlab.com/meltano/hub/-/issues/261#note_962943404 we'll should indicate that some files bundles aren't intended to be installed by themselves.
Ideally we could programmatically identify that based on the dependency relationships #251
@tayloramurphy Wanted to circle back to this. Should I be look at something in the Files YAML files or looking elsewhere to determine dependency relationships?
@alexmarple I think we're ok to hold off on this for now. The files that are a dependency of other plugins are indicated in a text field on the page right now https://hub.meltano.com/files/files-airflow
The bundles are referenced in the parent plugin in a field like this though https://github.com/meltano/hub/blob/main/_data/meltano/orchestrators/airflow/apache.yml#L9-L12
I'd say we want to make this distinction clear in the gridsome redesign, but for Hub Classic I'm ok with the current solution.
