Android GraphQL API Multi Auth: amplifyconfiguration.json does not update to include apiname

[sang2412]

Before opening, please confirm:

• [X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
• [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.

How did you install the Amplify CLI?

npm

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

No response

Amplify CLI Version

10.0.0

What operating system are you using?

Windows

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No manual changes made

Amplify Categories

auth, api

Amplify Commands

Not applicable

Describe the bug

When using Amplify CLI to configure a graphql API with multiple authorization modes, amplifyconfiguration.json does not get updated completely. The required configuration under awsAPIPlugin is not done for the additional authorization mode.

The documentation clearly mentions -

The friendly_name illustrated here is created from Amplify CLI prompt.

Expected behavior

In amplifyconfiguration.json, the required configuration under awsAPIPlugin should automatically be done for the additional authorization mode, as mentioned in the documentation.

Reproduction steps

1. Add a GraphQL API to an Android project using the Amplify CLI
2. In authorization modes, choose Cognito User Pools as the primary one and IAM as the additional authorization modes.
3. After completing the configuration, run Amplify Push.
4. Check if amplifyconfiguration.json is updated correctly. Check if configuration for additional auth is done automatically under "awsAPIPlugin" as mentioned in the documentation.

GraphQL schema(s)

```graphql # Put schemas below this line ```

Log output

``` # Put your logs below this line ```

Additional information

No response

[josefaidt]

Hey @sang2412 :wave: thanks for raising this! I was able to reproduce this issue and noticed the following awsAPIPlugin block:

"awsAPIPlugin": {
  "814": {
      "endpointType": "GraphQL",
      "endpoint": "https://pe7uiod2xnhajlqvwpn7ernexa.appsync-api.us-east-1.amazonaws.com/graphql",
      "region": "us-east-1",
      "authorizationType": "AMAZON_COGNITO_USER_POOLS",
      "apiKey": "da2-6qocwp27ungjbefd76n3vbboha"
  }
}

Marking as a bug 🙂

[sang2412]

Hi @josefaidt In the mean time, is it recommended to manually configure the awsAPIPlugin block? Hoping there won't be any security concerns with manual configuration.

[josefaidt]

Hey @sang2412 apologies for the delay here, but you should be able to add additional configs manually to the Amplify client in your app code as this file is prone to be overwritten