Open agardnerIT opened 2 years ago
Hi, and thanks for this overview. The idea of the artifacthub repo is to list all integrations, as you mentioned.
The idea is that every owner can enter their service, and especially if you have a dedicated GitHub repo for it, we have some automation (e.g., a new release of prometheus-service will automatically create a Pull Request in Artifacthub)
There are some exceptions that I would like to mention:
There are some more integrations that I'm not too happy with being listed, e.g., litmus-service and locust-service. Locust-service can easily be replaced with a proper job-executor-service example (we already have one here: https://github.com/keptn-contrib/job-executor-service/blob/main/FEATURES.md#kubernetes-job Litmus-service is not maintained at all, ...
Last but not least, datadog-service: That's a rather new integration. If it works, we are happy to accept it to the artifacthub repo.
Long story short: We should provide our end-users the best possible experience by offering working integrations (not every integration) on ArtifactHub. We are not locking anyone out, but we are not pro-actively adding old and most likely non-working integrations.
Currently Keptn has 4 potential places that tooling integration can be found:
Users of Keptn won't understand this and will just look at the Integrations page of Keptn.sh and see very few tooling integrations.
This issue suggests that all proven and actively maintained tooling integrations should be listed on artifactHub as the "one stop shop".
If integrations are still in incubating status, perhaps a warning is added to artifacthub?
Relates to #42