[rule based autotagging] Add Delete Rule API Logic#18184
[rule based autotagging] Add Delete Rule API Logic#18184jainankitk merged 15 commits intoopensearch-project:mainfrom
Conversation
Signed-off-by: Lingxi Chen <lingxich@amazon.com>
Signed-off-by: Lingxi Chen <lingxich@amazon.com>
|
❌ Gradle check result for 5129a79: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: Lingxi Chen <lingxich@amazon.com>
|
❌ Gradle check result for c6a1825: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: Lingxi Chen <lingxich@amazon.com>
|
❌ Gradle check result for f37990f: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: Lingxi Chen <lingxich@amazon.com>
Signed-off-by: Lingxi Chen <lingxich@amazon.com>
|
❌ Gradle check result for 1669731: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
@jainankitk For Feature Type we're keeping it to get the RulePersistenceService from the Registry class |
Signed-off-by: Lingxi Chen <lingxich@amazon.com>
|
❌ Gradle check result for 5e38cb0: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
@Lindsay-00 - Can you resolve the failing precommit and other checks? |
Signed-off-by: Lingxi Chen <lingxich@amazon.com>
|
❌ Gradle check result for 0d33419: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
@Lindsay-00 - Precommit is still failing. Maybe you can try running it locally to verify? Also, can you add changelog entry? |
Signed-off-by: Lingxi Chen <lingxich@amazon.com>
Signed-off-by: Lingxi Chen <lingxich@amazon.com>
|
❌ Gradle check result for 2120016: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
@Lindsay-00 - Failures look related, can you check: |
Signed-off-by: Lingxi Chen <lingxich@amazon.com>
|
❌ Gradle check result for f1f0783: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Thanks for pointing it out! Just fixed them. |
|
❌ Gradle check result for f1f0783: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
❌ Gradle check result for 7f90f40: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
❌ Gradle check result for 7f90f40: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
❌ Gradle check result for 7f90f40: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
❌ Gradle check result for 7f90f40: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
@Lindsay-00 - Can you check the build log for issues? - https://build.ci.opensearch.org/job/gradle-check/58062/console. cc: @kaushalmahi12 |
Signed-off-by: Lingxi Chen <lingxich@amazon.com>
…penSearch into delete-rule-api-pr-v2
|
❌ Gradle check result for 1ea4330: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Signed-off-by: Lingxi Chen <lingxich@amazon.com>
|
❕ Gradle check result for cddf074: UNSTABLE Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #18184 +/- ##
============================================
+ Coverage 72.48% 72.52% +0.03%
- Complexity 67357 67385 +28
============================================
Files 5488 5492 +4
Lines 311023 311076 +53
Branches 45217 45218 +1
============================================
+ Hits 225444 225606 +162
+ Misses 67282 67063 -219
- Partials 18297 18407 +110 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…t#18184) Signed-off-by: Lingxi Chen <lingxich@amazon.com> Co-authored-by: Lingxi Chen <lingxich@amazon.com>
…t#18184) Signed-off-by: Lingxi Chen <lingxich@amazon.com> Co-authored-by: Lingxi Chen <lingxich@amazon.com>Signed-off-by: TJ Neuenfeldt <tjneu@amazon.com>
…t#18184) Signed-off-by: Lingxi Chen <lingxich@amazon.com> Co-authored-by: Lingxi Chen <lingxich@amazon.com>
Description
This PR introduces the Delete Rule API Logic.
Related Issues
Resolves #[Issue number to be closed when this PR is merged]
Check List
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.