Skip to content
This repository has been archived by the owner on Oct 15, 2024. It is now read-only.

Alexa Lex created LexBot, LexIntent cannot be deleted when the bot has an alias configured #622

Closed
deekayw0n opened this issue Mar 29, 2021 · 0 comments · Fixed by #719
Closed

Comments

@deekayw0n
Copy link

deekayw0n commented Mar 29, 2021

aws-nuke fails to delete LexBot and LexIntent resources when an alias is associated to the bot. Manual removal of the alias in the console or CLI allows it to complete the deletion as expected.

Errors:

us-west-2 - LexBot - testbot - [Name: "testbot", Status: "READY"] - failed
s-west-2 - LexIntent - weather - [Name: "weather"] - failed
ERRO[0030] There are resources in failed state, but none are ready for deletion, anymore. 
us-west-2 - LexBot - testbot - [Name: "testbot", Status: "READY"] - failed
ERRO[0030] ResourceInUseException: 
{
  RespMetadata: {
    StatusCode: 400,
    RequestID: "158d2337-04bb-4cbc-9a66-3d9531241d92"
  },
  ExampleReference: {
    Name: "testerbot"
  },
  ReferenceType: "BotAlias"
} 
us-west-2 - LexIntent - weather - [Name: "weather"] - failed
ERRO[0030] ResourceInUseException: 
{
  RespMetadata: {
    StatusCode: 400,
    RequestID: "d342575f-9b39-46f7-ba13-47293c6cb34b"
  },
  ExampleReference: {
    Name: "testbot",
    Version: "$LATEST"
  },
  ReferenceType: "Bot"
} 
Error: failed

After: aws lex-models delete-bot-alias --name testerbot --bot-name testbot --region us-west-2:

us-west-2 - LexIntent - weather - [Name: "weather"] - removed
us-west-2 - LexBot - testbot - [Name: "testbot", Status: "READY"] - removed

Nuke complete: 0 failed ....
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant