Closed heitorlessa closed 5 years ago
FWIW, I've also tried running amplify configure project
as per other similar issues but still not working.
I suspect this may be due being a new laptop and I copied the files over. Here's the file structure just in case something is missing:
amplify
├── #current-cloud-backend
│ ├── amplify-meta.json
│ ├── api
│ │ └── awsserverlessairline
│ │ ├── build
│ │ │ ├── cloudformation-template.json
│ │ │ ├── functions
│ │ │ ├── parameters.json
│ │ │ ├── pipelineFunctions
│ │ │ ├── resolvers
│ │ │ │ ├── Booking.inboundFlight.req.vtl
│ │ │ │ ├── Booking.inboundFlight.res.vtl
│ │ │ │ ├── Booking.outboundFlight.req.vtl
│ │ │ │ ├── Booking.outboundFlight.res.vtl
│ │ │ │ ├── Mutation.createBooking.req.vtl
│ │ │ │ ├── Mutation.createBooking.res.vtl
│ │ │ │ ├── Mutation.createFlight.req.vtl
│ │ │ │ ├── Mutation.createFlight.res.vtl
│ │ │ │ ├── Mutation.deleteBooking.req.vtl
│ │ │ │ ├── Mutation.deleteBooking.res.vtl
│ │ │ │ ├── Mutation.deleteFlight.req.vtl
│ │ │ │ ├── Mutation.deleteFlight.res.vtl
│ │ │ │ ├── Mutation.updateBooking.req.vtl
│ │ │ │ ├── Mutation.updateBooking.res.vtl
│ │ │ │ ├── Mutation.updateFlight.req.vtl
│ │ │ │ ├── Mutation.updateFlight.res.vtl
│ │ │ │ ├── Query.getBooking.req.vtl
│ │ │ │ ├── Query.getBooking.res.vtl
│ │ │ │ ├── Query.getFlight.req.vtl
│ │ │ │ ├── Query.getFlight.res.vtl
│ │ │ │ ├── Query.listBookings.req.vtl
│ │ │ │ ├── Query.listBookings.res.vtl
│ │ │ │ ├── Query.listFlights.req.vtl
│ │ │ │ └── Query.listFlights.res.vtl
│ │ │ ├── schema.graphql
│ │ │ └── stacks
│ │ │ ├── Booking.json
│ │ │ ├── ConnectionStack.json
│ │ │ ├── CustomResources.json
│ │ │ └── Flight.json
│ │ ├── parameters.json
│ │ ├── resolvers
│ │ ├── schema.graphql
│ │ └── stacks
│ │ └── CustomResources.json
│ ├── auth
│ │ └── cognitoa7d29d9d
│ │ ├── cognitoa7d29d9d-cloudformation-template.yml
│ │ └── parameters.json
│ └── backend-config.json
├── aws-info.json
├── backend
│ ├── amplify-meta.json
│ ├── api
│ │ └── awsserverlessairline
│ │ ├── build
│ │ │ ├── cloudformation-template.json
│ │ │ ├── functions
│ │ │ ├── parameters.json
│ │ │ ├── pipelineFunctions
│ │ │ ├── resolvers
│ │ │ │ ├── Booking.inboundFlight.req.vtl
│ │ │ │ ├── Booking.inboundFlight.res.vtl
│ │ │ │ ├── Booking.outboundFlight.req.vtl
│ │ │ │ ├── Booking.outboundFlight.res.vtl
│ │ │ │ ├── Mutation.createBooking.req.vtl
│ │ │ │ ├── Mutation.createBooking.res.vtl
│ │ │ │ ├── Mutation.createFlight.req.vtl
│ │ │ │ ├── Mutation.createFlight.res.vtl
│ │ │ │ ├── Mutation.deleteBooking.req.vtl
│ │ │ │ ├── Mutation.deleteBooking.res.vtl
│ │ │ │ ├── Mutation.deleteFlight.req.vtl
│ │ │ │ ├── Mutation.deleteFlight.res.vtl
│ │ │ │ ├── Mutation.updateBooking.req.vtl
│ │ │ │ ├── Mutation.updateBooking.res.vtl
│ │ │ │ ├── Mutation.updateFlight.req.vtl
│ │ │ │ ├── Mutation.updateFlight.res.vtl
│ │ │ │ ├── Query.getBooking.req.vtl
│ │ │ │ ├── Query.getBooking.res.vtl
│ │ │ │ ├── Query.getFlight.req.vtl
│ │ │ │ ├── Query.getFlight.res.vtl
│ │ │ │ ├── Query.listBookings.req.vtl
│ │ │ │ ├── Query.listBookings.res.vtl
│ │ │ │ ├── Query.listFlights.req.vtl
│ │ │ │ └── Query.listFlights.res.vtl
│ │ │ ├── schema.graphql
│ │ │ └── stacks
│ │ │ ├── Booking.json
│ │ │ ├── ConnectionStack.json
│ │ │ ├── CustomResources.json
│ │ │ └── Flight.json
│ │ ├── parameters.json
│ │ ├── resolvers
│ │ ├── schema.graphql
│ │ └── stacks
│ │ └── CustomResources.json
│ ├── auth
│ │ └── cognitoa7d29d9d
│ │ ├── cognitoa7d29d9d-cloudformation-template.yml
│ │ └── parameters.json
│ ├── awscloudformation
│ │ └── nested-cloudformation-stack.yml
│ └── backend-config.json
└── team-provider-info.json
Working!
Steps to solve:
amplify/.config/aws-info.json
amplify configure project
amplify auth update
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.
Looking for a help forum? We recommend joining the Amplify Community Discord server *-help
channels for those types of questions.
Describe the bug Fresh new installation of amplify CLI using Node 10 under NVM, and despite a few installation errors with
gyp
andzmq
which I suspect is due tomock feature
, I cannot run make update operations.Project in question is: https://github.com/aws-samples/aws-serverless-airline-booking
It seems that the latest version introduced a bug where it expects
IdentityPoolId
, so in order to fix it I'm trying to runamplify auth update
using the latest version -- As per instructions here: https://github.com/aws-amplify/amplify-cli/issues/2096While it worker in another developer laptop, mine it doesn't - It must be some dependency that I have to install that I may not have in the new laptop.
To Reproduce Steps to reproduce the behavior:
npm install -g @aws-amplify/cli
amplify init
amplify auth update
Expected behavior A clear and concise description of what you expected to happen.
Auth category to be updated.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
amplify -v
: 1.12.0Additional context
Stack error when trying to update
auth
, and full stack error when trying to install amplify cli.