Continuous Execution + Execute API #462
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Ronnak Saxena <[email protected]>
Closed
|
Need to finish TransportExecutePolicy by extracting managedIndexConfig from requested index and passing it into runner.runJob method. |
Closed
|
This was worked by an intern. Can we close this @bowenlan-amzn? |
|
Closing this. Please open a new PR if you want to finish it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Ronnak Saxena [email protected]
Issue #, if available:
#281
#48
Description of changes:
Changed ISM policy execution to allow an option for continuous exeuciton with E2E testing. Started development on additional Execute API to immediately execute policy for specified managed index.
CheckList:
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.