aws-amplify / aws-amplify/amplify-cli
Amplify Push fails with: Parameters: [access, type] must have values
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
### How did you install the Amplify CLI?
npm
### If applicable, what version of Node.js are you using?
18.7.0
### Amplify CLI Version
10.8.1
### What operating system are you using?
Windows
### 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 added predictions to the amplify local backend using amplify cli,
```
amplify predictions add
√ Please select from one of the categories below · Identify
√ What would you like to identify? · Identify Labels
√ Provide a friendly name for your resource · identifyLabelsbc2c037f
√ Would you like to use the default configuration · Default Configuration
√ Who should have access? · Auth users only
```
I didn't edit the local backend files and when I tried to push:
```
🛑 The following resources failed to deploy:
Resource Name: predictionsidentifyLabelsbc2c037f (AWS::CloudFormation::Stack)
Event Type: create
Reason: Parameters: [access, type] must have values
🛑 Resource is not in the state stackUpdateComplete
Name: predictionsidentifyLabelsbc2c037f (AWS::CloudFormation::Stack), Event Type: create, Reason: Parameters: [access, type] must have values
```
### Expected behavior
To push the backend successfully.
### Reproduction steps
1. Add predictions
2. Push
### Project Identifier
e5c65903e25dce83b476572ec4ab9dc3
### Log output
```
# Put your logs below this line
🛑 The following resources failed to deploy:
Resource Name: predictionsidentifyLabelsbc2c037f (AWS::CloudFormation::Stack)
Event Type: create
Reason: Parameters: [access, type] must have values
🛑 Resource is not in the state stackUpdateComplete
Name: predictionsidentifyLabelsbc2c037f (AWS::CloudFormation::Stack), Event Type: create, Reason: Parameters: [access, type] must have values
```
### Additional information
_No response_
### Before submitting, please confirm:
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.
Contributor guide
Research direction
Reproduce the failure with `amplify predictions add` followed by `amplify push` using the reported Node.js, Amplify CLI, and Windows setup. Inspect the generated local prediction resource and its deployment parameters; done means the backend pushes successfully without the missing `access` and `type` parameter error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, nodejs
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100