fix(delete): Remove Deletion Polling #2
Closed
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.
Hi there! We noticed an issue deleting Lex bot resources when using this custom resource due to the polling/async behaviour in the
crhelper
library.I've tested the changes in the PR against our own larger bot definition and they seem to correctly delete the resource with the polling strategy removed.
Issue #, if available:
resolves: #1
Description of changes:
AWS::Events::Rule
resources that arecreated by the
crhelper
library to implement a pollingstrategy for the custom resource.
update
andcreate
were previouslyremoved in commit ad497ce, but
the
poll_delete
function was not removed.correctly creates and updates the bot resource, but it will
fail on deletion with an error message of:
poll_delete
functionand update the
delete_resource
function to wait for the botand the bot alias to be fully deleted.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.