-
Notifications
You must be signed in to change notification settings - Fork 273
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
[release]: Publish opensearch-reporting-cli to npm #3112
Comments
Closing #3113 as it is related to the same component. Will track |
@rupal-bq Could you please provide a tentative release date to be better prepared? |
Can we do first week of Feb? |
Hi @rupal-bq , Sure we can start with the process accordingly. Can you fix the date and update the issue with the same? |
Thanks @gaiksaya. I updated the date in issue description. Yes, url will should be similar to other components on download page. |
@gaiksaya can we have a release date for this please, thanks |
Sorry got busy with another release. I was trying to create a different role for each component with limited access to uploading path in S3 however there is some blocker as it was a 3 hop role assumption. We are moving forward with manual role creation for now. Thanks! |
Looks like the artifact that will be published to artifacts.opensearch.org is |
@gaiksaya Thank you for helping with the release. |
What is the name of your component?
opensearch-reporting-cli
What is the link to your GitHub repo?
https://github.com/opensearch-project/reporting-cli
Targeted release date
Feb 2, 2023
Where should we publish this component?
https://www.npmjs.com/
Publish tgz to artifacts.opensearch.org
What type of artifact(s) will be generated for this component?
npm package
Have you completed the required reviews including security reviews, UX reviews?
Yes
Have you on-boarded automated security scanning for the GitHub repo associated with this component?
Yes
Additional context
No response
The text was updated successfully, but these errors were encountered: