Amplifyconfiguration.dart keeps pulling the wrong api key from the amplify console

[superSaen42]

Before opening, please confirm:

• [X] I have searched for duplicate or closed issues.
• [X] I have read the guide for submitting bug reports.
• [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• [X] I have removed any sensitive information from my code snippets and submission.

App Id

d3q8xhp8f5zb3m

Region

us-east-1

Environment name

devclone

Figma File Version (if applicable)

No response

Amplify CLI Version

12.10.0

If applicable, what version of Node.js are you using?

No response

What operating system are you using?

Mac

Browser type?

Chrome

Describe the bug

My Appsync api key recently expired so I rotated the key in the appsync UI. The change is reflected in my amplify console because I can see the new API key when I go to the graphQL settings page in the Data section. However whenever I run amplify pull in my local terminal I get the old API key.

Expected behavior

When changing the api key in appsync I should be able to run amplify pull and the new api key should render in my amplifyconfiguration.dart file.

Reproduction steps

1. Change api key in Appsync UI
2. Amplify Updates api key for datastore
3. run amplify pull locally
4. see amplifyconfiguration.dart for new api key

Project Identifier

ca03b9303aff08e253440a24ab3d2e24

Additional information

No response

[ykethan]

Hey @superSaen42, manual changes on the console does not update the local pull as Amplify updates/creates resources using cloudforamtion template. The API key will need to updated via Amplify CLI or Studio GraphQL setting then run push/deploy to update the API key references.

[cwoolum]

Closing due to inactivity. Please re-open if necessary.

[github-actions[bot]]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.