Add the feature of showing useful error message during CI

[RyanL1997]

Signed-off-by: Ryan Liang jiallian@amazon.com

Description

Create a separate workflow and implemented environment variable of version to check for the existence of the OpenSearch Security Plugin artifact

Issues Resolved

• Resolved [Feature] Provide useful errors and next steps when this plugins dependencies are out of alignment #1073

Testing

CI test case#1 with "403 Forbidden" response
CI test case#2 with "404 Not Found" response
Created a new workflow for "Verify there is matching build of security plugin" by running prerequisites-test

Check List

• New functionality includes testing
• 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.

[codecov-commenter]

Codecov Report

Merging #1083 (cac0c5e) into main (7299822) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1083   +/-   ##
=======================================
  Coverage   72.27%   72.27%           
=======================================
  Files          87       87           
  Lines        1915     1915           
  Branches      244      244           
=======================================
  Hits         1384     1384           
  Misses        478      478           
  Partials       53       53           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[cwperks]

Is it possible to create variables in the Github actions files? We use the version in a number of places and it would be nice to define it once.

[RyanL1997]

Hi @cwperks. Thanks for the reply. I think we can only set up the environment variables in the Github actions files. I can definitely try to set it up in the environment variable to see if it works.

[peternied]

This would fail the integration-test workflow, what would you think about creating a separate workflow called something like prerequisites that could have a task named "Verify there is matching build of security plugin"

[RyanL1997]

Hi @peternied. Thanks for the reply! The reason I set to check it up here because if this one fails, the next test of Download OpenSearch Security Plugin will also be failed and break the integration-test. I was planning to use this test only as the prerequisite for checking the test of Download OpenSearch Security Plugin. Sorry for the confusions anyways. Please correct me if I miss some of the steps.

[peternied]

Here is the UI that our users would see on failures with the current design, might be useful to have this spelled out more plainly (Less clicks is better!)

[RyanL1997]

I think I get it now! Ya I will create a new work flow with a better name for running this separately! Thanks @peternied!

[RyanL1997]

He guys, I have made the update of this PR:

1. Instead of directly to implement the test in integration-test, I created a separate workflow called prerequisite-test.
2. Implemented the environment variable of version numbers in prerequisite-test
   Seems like it is also possible to setup the environment variable of version in the Integration-test. However, we may need another PR for doing that if it is necessary.

[cliu123]

@RyanL1997 Would you please add the new behavior in the PR description?

[cwperks]

The name of this should reflect what the check is performing. How does "Check for the existence of the OpenSearch Security Plugin artifact" sound?

[RyanL1997]

Sure, I have updated the commit and also changed the PR description with that. Thx for the review @cwperks!

[cwperks]

This name appears in the checks like this:

Shorten this to "Prerequisite Checks"?

[cwperks]

Similar to above: maybe "Run prerequisite checks"?

[RyanL1997]

Thanks! I have changed the name for both test's name and the sub tests' name. Please review it.