Changes Analysis

Commit SHA: 9eb972f
Comparing To SHA: 389a8de

API Changes

Summary

├─┬Paths
│ └──[➕] path (8967:3)
└─┬Components
  ├──[➕] responses (34482:7)
  └──[➕] schemas (63921:7)

• Total Changes: 3
• Additions: 3

Report

The full API changes report is available at: https://github.com/opensearch-project/opensearch-api-specification/actions/runs/13979359037/artifacts/2795779638

API Coverage

Thanks @jzonthemtn
This test is failing with 503 error.

Is this plugin part of 2.19? If so you don't need a custom plugins/user_behavior_insights folder, add the tests under default.

Is this plugin part of 2.19? If so you don't need a custom plugins/user_behavior_insights folder, add the tests under default.

No, it's not. Just 3.0. Thanks, will update.

Is this plugin part of 2.19? If so you don't need a custom plugins/user_behavior_insights folder, add the tests under default.

No, it's not. Just 3.0. Thanks, will update.

If it's (going to be) installed by default tests should go into default still and have version: >= 3.0. The plugins tests are for those that require custom setup.

Is this plugin part of 2.19? If so you don't need a custom plugins/user_behavior_insights folder, add the tests under default.

No, it's not. Just 3.0. Thanks, will update.

If it's (going to be) installed by default tests should go into default still and have version: >= 3.0. The plugins tests are for those that require custom setup.

@dblock Sorry, I'm not sure I follow. Are you saying I still don't have it quite right?

@dblock Sorry, I'm not sure I follow. Are you saying I still don't have it quite right?

1. The test is in the right place now, but tests/default/user_behavior_insights/initialize.yaml should be tests/default/ubi/initialize.yaml to match the route.
2. The tests run in CI in a big matrix of versions, so you need to make sure the test only runs on 3.0+ since your feature doesn't exist till then by adding version: 3.0. And you'll need to make sure the build of 3.0 used has your feature (and potentially bump the revision in the CI).

There's probably more. I'd start by making sure the tests pass locally for you.

@dblock Sorry, I'm not sure I follow. Are you saying I still don't have it quite right?

1. The test is in the right place now, but tests/default/user_behavior_insights/initialize.yaml should be tests/default/ubi/initialize.yaml to match the route.
2. The tests run in CI in a big matrix of versions, so you need to make sure the test only runs on 3.0+ since your feature doesn't exist till then by adding version: 3.0. And you'll need to make sure the build of 3.0 used has your feature (and potentially bump the revision in the CI).

There's probably more. I'd start by making sure the tests pass locally for you.

Thanks, I think that got me on the right path.

$ npm run test:spec -- --opensearch-url http://localhost:9200 --tests ./tests/default/ubi/

> [email protected] test:spec
> ts-node tools/src/tester/test.ts --opensearch-url http://localhost:9200 --tests ./tests/default/ubi/

[WARNING] No credentials provided, did you forget to set OPENSEARCH_PASSWORD or AWS_ACCESS_KEY_ID?
OpenSearch 3.0.0

PASSED  initialize.yaml (tests/default/ubi/initialize.yaml)

Tested 1/600 paths.