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

Expand Meshery's Integration with Artifact Hub #9966

Open
3 of 5 tasks
leecalcote opened this issue Jan 14, 2024 · 7 comments
Open
3 of 5 tasks

Expand Meshery's Integration with Artifact Hub #9966

leecalcote opened this issue Jan 14, 2024 · 7 comments
Labels
area/devops area/gitops framework/helm Issues related to helm-charts help wanted Extra attention is needed issue/willfix This issue will be worked on kind/epic An issue that describes a set of concerns (issues) kind/feature New major feature or request
Milestone

Comments

@leecalcote
Copy link
Member

leecalcote commented Jan 14, 2024

This issue is parent issue (labeled with kind/epic) with any number of associated child issues.

Current Behavior

After discussion with Artifact Hub maintainers, Meshery's proposed integration with Artifact Hub currently has the following action items to execute:

  1. Meshery Designs as a new Artifact Hub kind.
  2. Work with a handful of publishers to update their artifacthub screenshot annotation to use a Meshery snapshot.
  3. Write blog post for Artifact Hub highlighting this ability; evaluate broader publisher interest.
    Optional publisher inclusion of link to Meshery design - either editable in Playground or read-only, embedded somewhere (maybe that project's site).
  4. All of these being Meshery project action items, save for the part about an evaluation of broader interest - that being a collaborative assessment with decision left up to Artifact Hub.
  5. Artifact Hub facilitates the embedding of Meshery Designs as a native option offered of Artifact Hub. We'll need to build momentum and a proof point, first.

Implementation / Child Issues


Contributor Guides and Handbook

@leecalcote leecalcote added help wanted Extra attention is needed kind/epic An issue that describes a set of concerns (issues) kind/feature New major feature or request area/devops framework/helm Issues related to helm-charts area/gitops labels Jan 14, 2024
@leecalcote leecalcote added this to the v0.8.0 milestone Jan 14, 2024
@bytesSculptor
Copy link

Hey I want to work on this issue, under LFX mentorship.
I am new to DevOps, Can I also apply???
I have gained experience in docker, k8s, helm charts, will learn artifact hub also as it was mentioned in the Recommended Skills.
@aabidsofi19 @leecalcote i am also new to meshery, please guide me where should i start learning, right now i am just started exploring meshery
thanks

@leecalcote
Copy link
Member Author

Review this example - artifacthub/hub#3350 (comment).

@narasimha-1511
Copy link

narasimha-1511 commented Feb 21, 2024

i want to work on this? hey @leecalcote
under Gsoc ..

@hamza-mohd hamza-mohd added the issue/willfix This issue will be worked on label Mar 16, 2024
@ctcarrier
Copy link

@leecalcote I've been reviewing this issue today. In this issue item #1 refers to "Meshery patterns as a new Artifact Hub kind." and then the child ticket references Meshery Designs as a new Artifact Hub kind. Can you clarify if there are two different artifact types that are meant to be new Artifact Hub kinds or is this all specific to MeshMap Designs?

@leecalcote
Copy link
Member Author

@ctcarrier, thank you for asking. Please do proceed with "Designs" as the preferred and only term for this integration.

While Meshery will support "patterns" as a concept in a future release, "designs" are the base construct that users will broadly import/export and is the focus of the Artifact Hub integration.

@ctcarrier
Copy link

Questions to consider from the Meshery side:

  1. What repositoryID and owners to use in the artifacthub-repo.yml: https://github.com/artifacthub/hub/blob/master/docs/metadata/artifacthub-repo.yml
  2. Which repository to use as initial integration with AH. Needs at least 1 design. Designs should have a README and artifacthub-pkg.yml file: https://github.com/artifacthub/hub/blob/master/docs/metadata/artifacthub-pkg.yml
  3. From the AH team: Do designs use a single yaml file or multiple? It could be interesting to reference this file from the AH UI, or even consider displaying its contents at some point. So it'd be great if we could rely on some convention to locate it (i.e. a recommended file name, suffix, prefix, etc).

AH ticket for reference: artifacthub/hub#3720

cc @leecalcote

@tegioz
Copy link

tegioz commented Mar 20, 2024

Hi!

  1. What repositoryID and owners to use in the artifacthub-repo.yml: https://github.com/artifacthub/hub/blob/master/docs/metadata/artifacthub-repo.yml

The repository ID can be obtained from the AH control panel once you create the repository. It's only needed for some features (i.e. verified publisher), so you can take care of this a bit later if you'd like. Owners can be used to claim the ownership of a repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devops area/gitops framework/helm Issues related to helm-charts help wanted Extra attention is needed issue/willfix This issue will be worked on kind/epic An issue that describes a set of concerns (issues) kind/feature New major feature or request
Projects
Development

No branches or pull requests

6 participants