-
Notifications
You must be signed in to change notification settings - Fork 79
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
Cannot replace API key through Amplify CLI #3113
Comments
Hi @andylim0221, Thank you for bringing this up. To better understand the issue, could you confirm if a new API key was created in the AppSync console after adding |
Hi @AnilMaktala, the sequence is as below:
In this case, I did not update the schema and still the error happens. This issue is blocking me from pushing changes to the schema |
Hi @andylim0221, Thank you for the response. Based on the error message, Could you try the following steps:
Let me know if that resolves the issue. |
Hi @AnilMaktala, yes I tried the steps from the last comment:
It's not working as well: |
Hi @andylim0221 👋 . Could you please run below command and send us the project identifer? |
@AnilMaktala Hi, the project identifier is 9e21f4c90c8900e61aab6bb6ad4208ae |
Hi @andylim0221, Thank you for sharing the diagnosis report. Could you please download the [#current-cloud-backend.zip] file from the deployment bucket in the S3 console, compare the local schema with the schema in the current-cloud-backend folder, and let me know if you notice any differences? Also, by any chance, are you on Discord? |
@AnilMaktala Yes I'm in that Discord channel. There's no difference between the local schema and the schema in the current-cloud-backend folder. To be fair, this is quite urgent from our end since we have to deploy the schema changes to make the production, and this is hindering us from doing so. |
Hey @andylim0221, Could you please share your Discord username? |
My Discord username - yareyaredaze0709 |
Hey @andylim0221, Thanks for sharing your username! I’ll reach out to you on Discord, and we can coordinate there. |
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v20.18.0
Amplify CLI Version
12.14.0
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.
I removed the expired API key and created a new one.
Describe the bug
I then tried to make some changes in the schema. First, the error is
Event Type: update, Reason: API key not found
. Then, I added"CreateAPIKey": 0
inapi/<API>/parameter.json
and runamplify push
again. It generates new errorName: Table (AWS::DynamoDB::Table), Event Type: update, Reason: Resource handler returned message: "Cannot update GSI's properties other than Provisioned Throughput and Contributor Insights Specification. You can create a new GSI with a different name." (RequestToken: e442268c-da90-cbb5-c806-fe540682df4b, HandlerErrorCode: InvalidRequest), IsCustomResource: false
Expected behavior
Able to push from Amplify CLI
Reproduction steps
Project Identifier
No response
Log output
No response
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: