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

Add/Modify OSI options on Migration Console #643

Merged
merged 4 commits into from
May 14, 2024

Conversation

lewijacn
Copy link
Collaborator

@lewijacn lewijacn commented May 9, 2024

Description

This change makes the following minor modifications for our OSI migration setup for the migration console

  • Removes incorrect separate OSI pipeline IAM roles for source and target clusters. This must be the same role and have adjusted accordingly
  • Add option to include-index-regex. This allows a user to specify multiple selection regexes that we will use to select which indices to migrate when configuring the template for OSI. As a default we will still try to move everything except system indices if not specified.
  • Properly hookup missing CW log settings following OSI required conventions
  • Minor cleanup in spots of OSI script

Issues Resolved

[List any issues this PR will resolve]

Testing

Local and AWS testing

Check List

  • New functionality includes testing
    • All tests pass, including unit test, integration test and doctest
  • New functionality has been documented
  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

…et pipeline roles

Signed-off-by: Tanner Lewis <lewijacn@amazon.com>
Signed-off-by: Tanner Lewis <lewijacn@amazon.com>
Signed-off-by: Tanner Lewis <lewijacn@amazon.com>
Copy link
Member

@peternied peternied left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do we verify changes to the osi pipeline template?

Signed-off-by: Tanner Lewis <lewijacn@amazon.com>
@lewijacn
Copy link
Collaborator Author

How do we verify changes to the osi pipeline template?

Previously we didn't. Have added some unit tests around this area to give us some more confidence about what we are generating

Copy link

codecov bot commented May 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.72%. Comparing base (2ae2959) to head (a087c93).
Report is 14 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #643      +/-   ##
============================================
- Coverage     75.84%   75.72%   -0.13%     
+ Complexity     1545     1543       -2     
============================================
  Files           168      168              
  Lines          6446     6455       +9     
  Branches        574      575       +1     
============================================
- Hits           4889     4888       -1     
- Misses         1177     1187      +10     
  Partials        380      380              
Flag Coverage Δ
unittests 75.72% <ø> (-0.13%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@peternied
Copy link
Member

I'm going to walk through these instructions before doing a deeper dive into the change you've made - thanks for including the README.md @lewijacn

@lewijacn lewijacn merged commit ca3f8a8 into opensearch-project:main May 14, 2024
8 of 9 checks passed
@lewijacn lewijacn deleted the modify-osi-console-options branch May 23, 2024 20:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants