-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting error "Unknown command: config" #2056
Comments
Hey @tech-meppem, thank you for reaching out and reporting this. The Marking this as bug to update the command. |
I'm facing the same issue as support for GitLab Enterprise Edition is not available. When I run the following command as mentioned in the docs I get:
😕 Please support GitLab EE 🙏 |
I'm also getting this issue. I currently believe it's likely due to region issues, as the app is on a different region to our IAM Identify Centre. |
Hey @abarke @tech-meppem , does this app have a Gen 2 backend thats being hosted on a different app or is this just a frontend only app? |
For me, no other hosted app at the moment. |
Hey! I setup a new app in Gen 2 and chose the manual deployment. I zipped and uploaded my Nuxt Until now I have only been using The setup backend page seems a bit strange to me. Perhaps this flow needs a rethink. |
Hey folks, thank you for the information. The command allows generating the passed this information to the Amplify team for improvements. |
It would be really nice just to be able to create backends via the CLI, without the requirement to use a VCS. Right now we are locked out of all these features because GitLab EE is not a supported VCS when creating an app in Amplify. Shame really as this is a no-go for us and all those businesses on GitHub enterprise too. We need to look at other solutions. Firebase has a great CLI BTW. I would expect a command like this:
This would...
That would...
With option to switch backends...
DX could definitely be improved. Feel a bit frustrated and left out without GitLab integration 😞 difficult to sell it to management without those integrations. |
I think the page about setting up the backend is misleading and poorly worded then.
When step 3/3 of these instructions is:
It makes it seem like that is all there is to do. As in, you just need to manually generate the amplify_outputs.json file. But the "deploy updates" button deploys to the current app, not a new one. So the "instructions below" are not actually doing anything to help you setup a backend. I think I sort of understand the instructions a bit more now; it's instruction how to build your frontend to work with a backend. Not how to setup a backend. But the page is called "Setup backend", and does not actually have instructions on how to setup the backend, so it is all very misleading. |
The time this has taken with us having to mirror our GitLab Enterprise repo into CodeCommit and then, due to needing to build, mirror our private npm registry into CodeArtifact |
CodeCommit is no longer available to new customers 🙄 Checkmate for me ♟️ It would be nice to take a Heroku approach at least so I can push my code to a remote app so that it builds when I push to it. |
Environment information
Describe the bug
I'm trying to deploy to an amplify app using S3 buckets, not a repo (we're just doing feasibility / investigation POC).
So everything has been zipped, and uploaded to S3, then selecting S3 bucket, then that zip when deploying updates.
We are zipping up the build outputs only, not the full repo. The site loads fine, but now it comes to implementing backend.
But I cannot find much documentation or help for setting up the "backend" with manual deployment, as all examples use git repos with the "app settings" page.
The only thing I can find is this page:
https://eu-north-1.console.aws.amazon.com/amplify/apps/<appid>/branches/staging/backend-help
Which tells me to run a
npx ampx generate config
command.However, when running that command, the help text of the command is printed, followed by
"Error: Unknown command: config"
.config
is not listed as an available command forampx generate
, so I am wondering if there is a recent update has changed things.It's not listed here either: https://docs.amplify.aws/react/reference/cli-commands/#npx-ampx-generate
I cannot find anyone else facing this problem elsewhere. I have been searching extensively.
Reproduction steps
This is the command I'm running (with <appid> replaced), with the output:
The text was updated successfully, but these errors were encountered: