fix: generate correct auth mode for admin queries in amplifyconfiguration.json

[yuth]

Updated the fronted config files creator to have the correct authorization type for Admin Queries. The earlier implementation had AWS_IAM hardcoded. The updated config looks similar to this

{
  "api": {
        "plugins": {
                "AdminQueries": {
                    "endpointType": "REST",
                    "endpoint": "https://zzzz.execute-api.us-west-2.amazonaws.com/dev",
                    "region": "us-west-2",
                    "authorizationType": "AMAZON_COGNITO_USER_POOLS"
                }
            }
        }
    }
}

fix #6983

Description of changes

Issue #, if available

Description of how you validated changes

Checklist

• PR description included
• yarn test passes
• Tests are changed or added
• Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[kaustavghosh06]

For existing projects, what's the plan for mitigation? Will we auto-add the authorization type in amplify-meta.json?

[yuth]

For existing projects, what's the plan for mitigation? Will we auto-add the authorization type in amplify-meta.json?

We are not doing any migration work as the Admin Queries never worked in that case. The fix would be to remove the admin queries and add it back again to get the fix.

[kneekey23]

@yuth not a great solution, I updated my admin queries functions to have some custom code so removing and re-adding isn't a fun time. id rather just continue to manually fix it after an amplify push

[siegerts]

👋 Hi, this issue was referenced in the v4.50.2 release!

Check out the release notes here https://github.com/aws-amplify/amplify-cli/releases/tag/v4.50.2.