So you want to contribute code to this project? Excellent! We're glad you're here. Here's what you need to do.
Fork this repository on GitHub, and clone locally with git clone
.
You will need to install node.js, nvm, and yarn in your environment to properly pull down dependencies to build and bootstrap the plugin.
-
Download OpenSearch for the version that matches the OpenSearch Dashboards version specified in package.json.
-
Download and install the appropriate Anomaly Detection OpenSearch Plugin.
-
Download the OpenSearch Dashboards source code for the version specified in package.json you want to set up.
See the OpenSearch Dashboards contributing guide and developer guide for more instructions on setting up your development environment.
-
Change your node version to the version specified in
.node-version
inside the OpenSearch Dashboards root directory (this can be done with thenvm use
command). -
Create a
plugins
directory inside the OpenSearch Dashboards source code directory, ifplugins
directory doesn't exist. -
Check out this package from version control into the
plugins
directory. -
Run
yarn osd bootstrap
insideOpenSearch-Dashboards/plugins/anomaly-detection-dashboards-plugin
.
Ultimately, your directory structure should look like this:
.
├── OpenSearch-Dashboards
│ └──plugins
│ └── anomaly-detection-dashboards-plugin
To build the plugin's distributable zip simply run yarn build
.
Example output: ./build/anomaly-detection-dashboards-1.0.0.0.zip
In the base OpenSearch Dashboards directory, run
yarn start --no-base-path
Starts OpenSearch Dashboards and includes this plugin. OpenSearch Dashboards will be available on localhost:5601
.
yarn test:jest
Runs the plugin unit tests.
Integration tests for this plugin are written using the Cypress test framework. The tests are maintained in the central opensearch-dashboards-functional-test repository. Steps to run the tests:
- Spin up a cluster with the Anomaly Detection plugin (details) and Anomaly Detection Dashboards Plugin (details) installed.
- Checkout opensearch-dashboards-functional-test
- In the root directory of
opensearch-dashboards-functional-test
, run a command using Cypress CLI
For more details and an example, see the related GitHub workflow.
This codebase uses Prettier as our code formatter. All new code that is added has to be reformatted using the Prettier version listed in package.json
. In order to keep consistent formatting across the project developers should only use the prettier CLI to reformat their code using the following command:
yarn prettier --write <relative file path>
NOTE: There also exists prettier plugins on several editors that allow for automatic reformatting on saving the file. However using this is discouraged as you must ensure that the plugin uses the correct version of prettier (listed in
package.json
) before using such a plugin.
The Github workflow in backport.yml
creates backport PRs automatically when the
original PR with an appropriate label backport <backport-branch-name>
is merged to main with the backport workflow
run successfully on the PR. For example, if a PR on main needs to be backported to 1.x
branch, add a label
backport 1.x
to the PR and make sure the backport workflow runs on the PR along with other checks. Once this PR is
merged to main, the workflow will create a backport PR to the 1.x
branch.