Closed ladawellness closed 2 years ago
Hi @ladawellness 👋 Thanks for raising this issue. I was able to reproduce it following your reproduction steps. I will label this a bug and transfer it to the CLI repo.
Hey @ladawellness to echo what @chrisbonifacio said thanks for raising this! What you've experienced is a duplicate of https://github.com/aws-amplify/amplify-cli/issues/7906 and is being actively investigated! 🙂
Closing in favor of tracking existing issue. Please subscribe to #7906 for further updates
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.
Looking for a help forum? We recommend joining the Amplify Community Discord server *-help
channels for those types of questions.
Before opening, please confirm:
JavaScript Framework
Angular, React
Amplify APIs
Interactions
Amplify Categories
interactions
Environment information
Describe the bug
When running amplify add interactions command, and be asked the "how I would like the intent to be fulfilled?" question, I chose AWS Lambda Function. The result is that below stack:
Expected behavior
I should be able to proceeed and get both the Lex and Lambda configuration to be deployed from Amplify CLI.
Reproduction steps
Code Snippet
Log output
aws-exports.js
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response