-
Notifications
You must be signed in to change notification settings - Fork 283
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
Onboard Front end plugins onto publish to maven workflow #4337
Comments
Hi @derek-ho , What kind of artifacts are you looking for? Thanks! |
As @gaiksaya mentioned, we cannot publish node artifacts to Maven. There was a discussion to publish front end plugins to NPM and we were thinking of publishing the artifact with a |
OSD has its own package management system on top of NPM. it is a software not package library. no need to publish OSD to npm. Regarding plugin, it is also not architecture in a way could be consume as a typical npm package, therefore no need to publish npm https://github.com/opensearch-project/OpenSearch-Dashboards/blob/main/packages/README.md Artifacts are different story, it is good to support rpm, docker, brew, deb outside of raw art.gz/zip file which will simplify the admin effort for install and deployment |
@derek-ho , I hope the above comments have been helpful in addressing your query. I am going to close this ticket for now ,but please feel free to re-open it if necessary. Thank you. |
Is your feature request related to a problem? Please describe
For backend plugins, with every PR merge, an image is published - example: https://github.com/opensearch-project/observability/actions/runs/7268660153/job/19804910058, to https://aws.oss.sonatype.org/content/repositories/snapshots/org/opensearch. Is it possible for front end OSD and plugins to use the same or similar workflow to publish fresh artifacts?
Describe the solution you'd like
Similar to maven publish workflow for front end OSD and plugins
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: