Open tostavio opened 4 days ago
There seems to be a problem with the recent change from amplify
to ampx
.
Not even a simple npx amplify init
works anymore:
➜ npx amplify init
InvalidCommandError: Amplify Gen 2 CLI has been renamed to ampx
Resolution: Run again using the ampx command name:
npx ampx init
Then, running with ampx
...
➜ npx ampx init
ampx <command>
Commands:
ampx generate Generates post-deployment artifacts
ampx sandbox Starts the sandbox, observation mode for the deployment of the Amplify backend
yments
ampx pipeline-deploy Command to deploy backends in a customized CI/CD pipeline
e. This command is not intended to be used locally.
ampx configure <command> Configures AWS Amplify
ampx info Generates Amplify troubleshooting information
Options:
--debug Print debug logs to the console [boolean] [default: false]
-h, --help Show help [boolean]
-v, --version Show version number [boolean]
Error: You meant info?
If you've changed the commands, did you updated the documentation and instructions in somewhere?
Hey @tostavio, thank you for reaching out. The ampx
command is utilized in Amplify Gen 2 and amplify
in Amplify Gen 1.
Refer to documents providing information on Amplify Gen 2 commands and Amplify Gen 1 commands
The error could not determine executable to run
typically occurs if the npx ampx
command was run outside the root of the project containing the amplify backend packages. Could you verify if the command is being run at the root of your project?
transferring the issue to backend repository
Describe the bug The account configuration steps in the documentation don't work. There is no problem setting the IAM user, the local
aws configure sso
and other steps. But when I run:npx ampx sandbox
ornpx ampx sandbox --profile <profile-name>
, I get this error:npx ampx sandbox --profile <profile-name>
I followed the documentation exactly. I reinstalled node 22, cleared my
.aws
configuration files and started from 0.I tried adding
@aws-amplify/cli
globally, but it's still not working.It would be nice if at least the example worked, it's not enough that it's confusing. Apparently there's some secret step that's not in the documentation? :(
To Reproduce Steps to reproduce the behavior:
Expected behavior Something like the docs tell me that will go?
Screenshots N/A
Desktop (please complete the following information):
Additional context Full log here: