aws-amplify / aws-amplify/amplify-cli
`amplify override api` exits immediately if API is container-based
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
### How did you install the Amplify CLI?
pnpm
### If applicable, what version of Node.js are you using?
18
### Amplify CLI Version
10.7.2
### 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.
n/a
### Describe the bug
see title
### Expected behavior
CLI either allows overriding resource or informs the developer whether it is permitted/supported
### Reproduction steps
1. `amplify init -y`
2. `amplify configure project` > container-based deployments > enable
3. `amplify add api` > any template, I chose Node.js express
4. `amplify override api`
5. observe CLI exits
### Project Identifier
_No response_
### Log output
```
# Put your logs below this line
```
### 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 issue with the listed Amplify CLI commands, especially enabling container-based deployments before adding an API and running `amplify override api`. Trace the CLI entry point for that command and its container-based API handling; done means it either permits the override or clearly reports whether the operation is unsupported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, node.js, typescript
- Domain
- api, cli, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100