Update lychee action to use v1 instead of specific patch number and tune behaviors

.github/workflows/link-checker.yml

@@ -12,9 +12,9 @@ jobs:
       - uses: actions/checkout@v2
       - name: lychee Link Checker
         id: lychee
-        uses: lycheeverse/lychee-action@v1.5.4
+        uses: lycheeverse/lychee-action@v1
         with:
-          args: --accept=200,403,429 --exclude-mail **/*.html **/*.md **/*.txt **/*.json --exclude-file .lychee.excludes --exclude-path tests/
+          args: --verbose --max-retries 5 --retry-wait-time 10 --accept=200,403,429 --exclude-path tests/ ./
           fail: true
         env:
-          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.lychee.excludes → .lycheeignore

@@ -1,7 +1,16 @@
+# Copyright OpenSearch Contributors
+# SPDX-License-Identifier: Apache-2.0
+#
+# The OpenSearch Contributors require contributions made to
+# this file be licensed under the Apache-2.0 license or a
+# compatible open source license.
+
 http://staging-artifacts.cloudfront.net/*
 https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/*
 http://public.ecr.aws/data-prepper-container-repository
 https://www.dummy.com/*
 # Too many redirects in playground.opensearch.org due to not having user agent information
 # https://github.com/lycheeverse/lychee/issues/715
 https://playground.opensearch.org/*
+file://*
+https://build.ci.opensearch.org/generic-webhook-trigger/invoke*

DEVELOPER_GUIDE.md

@@ -99,7 +99,7 @@ Alternatively, run a command inside the virtualenv with pipenv run.
 
 ### Run Tests
 
-This project uses [pytest](https://docs.pytest.org/en/6.x/) to ensure Python code quality. See [tests](tests).
+This project uses [pytest](https://docs.pytest.org/en/) to ensure Python code quality. See [tests](tests).
 
 ```
 $ pipenv run pytest

README.md

@@ -291,7 +291,7 @@ See [developer guide](DEVELOPER_GUIDE.md) and [how to contribute to this project
 
 If you find a bug, or have a feature request, please don't hesitate to open an issue in this repository.
 
-For more information, see [project website](https://opensearch.org/) and [documentation](https://docs-beta.opensearch.org/). If you need help and are unsure where to open an issue, try [forums](https://discuss.opendistrocommunity.dev/).
+For more information, see [project website](https://opensearch.org/) and [documentation](https://opensearch.org/docs/). If you need help and are unsure where to open an issue, try [forums](https://discuss.opendistrocommunity.dev/).
 
 ## Code of Conduct
 

release-notes/opensearch-release-notes-1.2.2.md

@@ -2,7 +2,7 @@
 
 ## Release Highlights
 
-This patch releases updates the version of Log4j used in OpenSearch to Log4j 2.16.0 as recommended by the advisory in [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046).
+This patch releases updates the version of Log4j used in OpenSearch to Log4j 2.16.0 as recommended by the advisory in [CVE-2021-45046](https://www.cve.org/CVERecord?id=CVE-2021-45046).
 
 ### OpenSearch
 * Increment version to 1.2.2 and backport log4j upgrade to 2.16. ([#1728](https://github.com/opensearch-project/OpenSearch/pull/1728))

release-notes/opensearch-release-notes-1.2.3.md

@@ -2,7 +2,7 @@
 
 ## Release Highlights
 
-This patch releases updates the version of Log4j used in OpenSearch to Log4j 2.17.0 as recommended by the advisory in [CVE-2021-45105](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45105).
+This patch releases updates the version of Log4j used in OpenSearch to Log4j 2.17.0 as recommended by the advisory in [CVE-2021-45105](https://www.cve.org/CVERecord?id=CVE-2021-45105).
 
 ### OpenSearch
 

release-notes/opensearch-release-notes-2.1.0.md

@@ -157,7 +157,7 @@ ES
 * Bump to 2.1.0 compatibility ([#282](https://github.com/opensearch-project/anomaly-detection-dashboards-plugin/pull/282))
 
 ### Opensearch Alerting
-* Bumped version to 2.1.0, and gradle to 7.4.2. ([#475](https://github.com/opensearch-project/alerting/pull/475]))
+* Bumped version to 2.1.0, and gradle to 7.4.2. ([#475](https://github.com/opensearch-project/alerting/pull/475))
 
 
 ### Opensearch Alerting Dashboards Plugin

src/report_workflow/README.md

@@ -55,8 +55,8 @@ The test-report manifest includes the following attributes:
   - Find the bundle manifest under the DistributionManifest key. It contains information about the bundle artifacts used for testing. 
 ### _**How Do I See the CI Logs of This Test Run?**_
   - Access our Jenkins job: 
-    - For `OpenSearch`: `https://build.ci.opensearch.org/job/<__TestType__>/<__TestID__>/`. e.g. https://build.ci.opensearch.org/job/integ-test/1234/
-    - For `OpenSearch Dashboards`: `https://build.ci.opensearch.org/job/<__TestType__>-opensearch-dashboards/<__TestID__>/`. e.g. https://build.ci.opensearch.org/job/integ-test-opensearch-dashboards/1234/
+    - For `OpenSearch`: `https://build.ci.opensearch.org/job/<__TestType__>/<__TestID__>/`. e.g. `https://build.ci.opensearch.org/job/integ-test/<__TestID__>/`
+    - For `OpenSearch Dashboards`: `https://build.ci.opensearch.org/job/<__TestType__>-opensearch-dashboards/<__TestID__>/`. e.g. `https://build.ci.opensearch.org/job/integ-test-opensearch-dashboards/<__TestID__>/`
 ### _**Where Can I See Detailed Testing Logs or Service Logs (e.g., Local Cluster Logs, Testing Videos)?**_
   - You can find details in the component YAML file under `components/configs/yml` in this test-report manifest. The component YAML file includes local cluster logs, stdout & stderr files, specific testing logs, and Cypress videos.  
 ### _**Why Are Some Component Testing Results Missing or Unavailable?**_