Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixed alias3 contains error #918

Conversation

kohinoor98
Copy link
Contributor

@kohinoor98 kohinoor98 commented Nov 7, 2023

Description

alias3 gets removed as per instructions from sample_policy_alias_action.json. In the final contains verification we do not need to check for alias3.

Issues Resolved

#911

Check List

  • Commits are signed per the DCO using --signoff
  • Tested on Cypress for policies_spec.js

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.

Copy link

codecov bot commented Nov 7, 2023

Codecov Report

Merging #918 (d781bc0) into main (3401a88) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #918   +/-   ##
=======================================
  Coverage   63.36%   63.36%           
=======================================
  Files         341      341           
  Lines       11553    11553           
  Branches     2243     2243           
=======================================
  Hits         7321     7321           
  Misses       3658     3658           
  Partials      574      574           

@AWSHurneyt
Copy link
Contributor

AWSHurneyt commented Nov 7, 2023

@kohinoor98 the policies spec test is passing, but looks like an alias spec test started failing. Could you look into whether that's related to your changes?

@kohinoor98
Copy link
Contributor Author

Hi @AWSHurneyt,

The test case this PR is failing is flaky as tagged in #910 and the proposed solution is also created for it #920. Please guide on next steps.

Thanks,
KC

@AWSHurneyt
Copy link
Contributor

Hi @AWSHurneyt,

The test case this PR is failing is flaky as tagged in #910 and the proposed solution is also created for it #920. Please guide on next steps.

Thanks, KC

Ah thanks for that context. Approved.

@bowenlan-amzn bowenlan-amzn merged commit 461f563 into opensearch-project:main Nov 8, 2023
10 checks passed
opensearch-trigger-bot bot pushed a commit that referenced this pull request Nov 8, 2023
Signed-off-by: kohinoor98 <[email protected]>
Co-authored-by: bowenlan-amzn <[email protected]>
(cherry picked from commit 461f563)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
bowenlan-amzn added a commit that referenced this pull request Nov 8, 2023
(cherry picked from commit 461f563)

Signed-off-by: kohinoor98 <[email protected]>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: bowenlan-amzn <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants