You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
9/13 - Beta Release for Capture and Replay
9/27 - Beta Release for Historical Fetch with Capture and Replay updates
10/27 - Complete Migration Life Cycle
11/27 - AWS Solutions Library Release
Where should we publish this component?
At present, we release only tarballs and zip files for the migration repo. We would like these to be PGP signed, and for these artifacts to be referenced on this page: https://opensearch.org/downloads.html.
Ideally, there should be a mechanism that allows us to redirect users to the latest version of the tooling, as this tooling will not be tied to a specific OpenSearch release."
What type of artifact(s) will be generated for this component?
tgz and zip of repo.
Have you completed the required reviews including security reviews, UX reviews?
Security Review - Please update status here
Given that this tooling is command line driven no UX review is needed.
Have you on-boarded automated security scanning for the GitHub repo associated with this component?
Yes.
Additional context
We have a migrations release schedule for this week. It is a beta incremental release until we get to our 1.0 release (scheduled for 11/27) and it is not tied to any OpenSearch release. However, there are a few tasks we need to work through for this release:
Putting the artifacts (zip/tgz) from github onto s3. I read through the steps here but noticed many do not apply to a release decoupled from OpenSearch release.
Signing the artifacts - I can do this with pgp signer but need access to the role defined here
Did you read the on-boarding document
I reviewed this document but not sure if the procedures apply in this the migrations repo is not a plugin.
What is the name of your component?
OpenSearch Migrations
What is the link to your GitHub repo?
https://github.com/opensearch-project/opensearch-migrations
Targeted release date
9/13 - Beta Release for Capture and Replay
9/27 - Beta Release for Historical Fetch with Capture and Replay updates
10/27 - Complete Migration Life Cycle
11/27 - AWS Solutions Library Release
Where should we publish this component?
At present, we release only tarballs and zip files for the migration repo. We would like these to be PGP signed, and for these artifacts to be referenced on this page: https://opensearch.org/downloads.html.
Ideally, there should be a mechanism that allows us to redirect users to the latest version of the tooling, as this tooling will not be tied to a specific OpenSearch release."
What type of artifact(s) will be generated for this component?
tgz and zip of repo.
Have you completed the required reviews including security reviews, UX reviews?
Security Review - Please update status here
Given that this tooling is command line driven no UX review is needed.
Have you on-boarded automated security scanning for the GitHub repo associated with this component?
Yes.
Additional context
We have a migrations release schedule for this week. It is a beta incremental release until we get to our 1.0 release (scheduled for 11/27) and it is not tied to any OpenSearch release. However, there are a few tasks we need to work through for this release:
The text was updated successfully, but these errors were encountered: