Description
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
16.3.2
Amplify CLI Version
10.8.1
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
I ran "amplify add predictions" with the following options:
Evertsons-MacBook-Pro:theamplifyapp evertsoncroes$ amplify add predictions
✔ Please select from one of the categories below · Identify
✔ What would you like to identify? · Identify Text
✔ Provide a friendly name for your resource · identifyTextd230b04a
✔ Would you also like to identify documents? (y/N) · yes
✔ Who should have access? · Auth users only
Successfully added resource identifyTextd230b04a locally
When running Amplify push I got the following error:
Name: predictionsidentifyTexte10c3610 (AWS::CloudFormation::Stack), Event Type: create, Reason: Parameters: [access, format, identifyDoc] must have values
When I checked the parameters.json, I can see indeed that these 3 values are missing. It seems the CLI is not generating the correct values based on my choices.
Expected behavior
That "amplify push" succeeds.
Reproduction steps
- Check out this project at this commit: https://gitlab.com/evertson90/theamplifyapp/-/commit/87db85a1acf0bf057fc86070cf3271d6990540c8
- run "amplify add predictions"
- See "describe the bug" section for answers I used
- run "amplify push"
Project Identifier
bfaf6cb7a4743f03f665dbc0848381fe
Log output
# Put your logs below this line
🛑 Resource is not in the state stackUpdateComplete
Name: predictionsidentifyTexte10c3610 (AWS::CloudFormation::Stack), Event Type: create, Reason: Parameters: [access, format, identifyDoc] must have values
Additional information
I haven't used this project since june 2022. So the sudden jump of Amplify versions might be the problem.
Before submitting, please confirm:
- I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- I have removed any sensitive information from my code snippets and submission.