aws-amplify / aws-amplify/amplify-cli
support a `path` argument to `amplify plugin add`
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
### Is this feature request related to a new or existing Amplify category?
New category
### Is this related to another service?
_No response_
### Describe the feature you'd like to request
Support a `path` argument on `amplify plugin add` to simplify command:
`amplify plugin add --path $(pnpm root -g)/amplify-graphql-seed-plugin`
Currently we need to first capture the absolute path, and paste it in to the required prompt
```console
> echo $(pnpm root -g)/amplify-graphql-seed-plugin | pbcopy
> amplify plugin add
? Enter the absolute path for the root of the plugin directory:
/Users/josef/Library/pnpm/global/5/node_modules/amplify-graphql-seed-plugin
Successfully added plugin package.
? Run a fresh scan for plugins on the Amplify CLI pluggable platform Yes
```
### Describe the solution you'd like
see above
### Describe alternatives you've considered
n/a
### Additional context
_No response_
### Is this something that you'd be interested in working on?
- [ ] 👋 I may be able to implement this feature request
### Would this feature include a breaking change?
- [ ] ⚠️ This feature might incur a breaking change
Contributor guide
Research direction
Start at the CLI implementation and argument parsing for `amplify plugin add`; trace how the current interactive absolute-path prompt is reached. Add support for the requested `--path` value and verify that the command can add the plugin without requiring the path prompt.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100