aws-amplify / aws-amplify/amplify-cli
`InvalidParameterException: client_id, client_secret and authorize_scopes are all required idp details.`
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
### Before opening, please confirm:
- [X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-cli/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/master/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
### How did you install the Amplify CLI?
curl
### If applicable, what version of Node.js are you using?
v17.0.1
### Amplify CLI Version
7.5.6
### What operating system are you using?
Mac os Big sur
### Amplify Categories
auth, function, api, notifications
### Amplify Commands
push
### Describe the bug
Amplify-CLI can not add modules (analytics, function and etc.)
We get an error message -- 🛑 An error occurred during the push operation: Resource is not in the state stackUpdateComplete after "amplify push"
### Expected behavior
Command "amplify push" should work or maybe we made mistake in setup for aws project
We need help
### Reproduction steps
Create project -- "amplify init"
Add Auth module -- "amplify add auth"
add login mechanism Google from AdminUI
turn on Enable access to unauthenticated identities
add a new Date model from admin UI
### GraphQL schema(s)
_No response_
### Log output

### Additional information
We think.
maybe, we have a conflict between different authorization modes (Api key mode and Cognito user pool mode)
Contributor guide
Research direction
Start by reproducing the reported flow with `amplify init`, `amplify add auth`, the AdminUI Google login setup, a new data model, and `amplify push`. Compare the CLI output with the reported `InvalidParameterException` and `stackUpdateComplete` failure; done means the configured modules can be pushed successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- api, authentication, cli, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100