fix(amplify-category-auth): update front end config on pull

[lazpavel]

Description of changes

• ensure that for projects created before 5.2.0, on pull we populate the auth frontend config

Description of how you validated changes

• yarn test passes,
• manual testing by creating a project with an older Amplify CLI and pulling into an empty folder populates the front end configuration

Checklist

• PR description included
• yarn test passes

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

[ericclemmons]

When running $(yarn global bin)/amplify-dev pull against my backend created via Amplify CLI in July (https://github.com/aws-amplify/amplify-ui/tree/main/environments/auth-with-username-no-attributes), I'm getting the following aws-exports.js with an empty aws_cognito_login_mechanisms:

/* eslint-disable */
// WARNING: DO NOT EDIT. This file is automatically generated by AWS Amplify. It will be overwritten.

const awsmobile = {
    "aws_project_region": "us-east-1",
    "aws_cognito_identity_pool_id": "us-east-1:******",
    "aws_cognito_region": "us-east-1",
    "aws_user_pools_id": "us-east-1_******",
    "aws_user_pools_web_client_id": "******",
    "oauth": {},
    "aws_cognito_login_mechanisms": [],
    "aws_cognito_signup_attributes": [
        "EMAIL"
    ],
    "aws_cognito_mfa_configuration": "OFF",
    "aws_cognito_mfa_types": [
        "SMS"
    ],
    "aws_cognito_password_protection_settings": {
        "passwordPolicyMinLength": 8,
        "passwordPolicyCharacters": []
    }
};


export default awsmobile;

Is username a default value somewhere? It shows up correctly in https://us-east-1.admin.amplifyapp.com/admin/d2zuq5rjkps8u4/dev/auth:

This what's in my parameters.json:

{
    "identityPoolName": "authwithusernamenoat3aaa0954_identitypool_3aaa0954",
    "allowUnauthenticatedIdentities": false,
    "resourceNameTruncated": "authwi3aaa0954",
    "userPoolName": "authwithusernamenoat3aaa0954_userpool_3aaa0954",
    "autoVerifiedAttributes": [
        "email"
    ],
    "mfaConfiguration": "OFF",
    "mfaTypes": [
        "SMS Text Message"
    ],
    "smsAuthenticationMessage": "Your authentication code is {####}",
    "smsVerificationMessage": "Your verification code is {####}",
    "emailVerificationSubject": "Your verification code",
    "emailVerificationMessage": "Your verification code is {####}",
    "defaultPasswordPolicy": false,
    "passwordPolicyMinLength": 8,
    "passwordPolicyCharacters": [],
    "requiredAttributes": [
        "email"
    ],
    "userpoolClientGenerateSecret": false,
    "userpoolClientRefreshTokenValidity": 30,
    "userpoolClientWriteAttributes": [
        "email"
    ],
    "userpoolClientReadAttributes": [
        "email"
    ],
    "userpoolClientLambdaRole": "authwi3aaa0954_userpoolclient_lambda_role",
    "userpoolClientSetAttributes": false,
    "sharedId": "3aaa0954",
    "resourceName": "authwithusernamenoat3aaa0954",
    "authSelections": "identityPoolAndUserPool",
    "authRoleArn": {
        "Fn::GetAtt": [
            "AuthRole",
            "Arn"
        ]
    },
    "unauthRoleArn": {
        "Fn::GetAtt": [
            "UnauthRole",
            "Arn"
        ]
    },
    "useDefault": "default",
    "userPoolGroupList": [],
    "serviceName": "Cognito",
    "usernameCaseSensitive": false,
    "dependsOn": []
}

I don't see a username specified anywhere in paramters.json nor my cloudformation template.

[attilah]

@ericclemmons asked me to take a look at the PR so even if it is a draft I reviewed it to give some directions for the future changes.

[cjihrig]

Is it possible to add a test for this?

[attilah]

I agree with @cjihrig's comments, please fix those before merging.

Regarding the awsexports (and others) generation make sure we have a test that preserves the custom values if they were present and also have a test for removal, when someone removes auth and such, then the configured values MUST be removed from awsexports (and others)

[github-actions]

👋 Hi, this pull request was referenced in the v5.6.0 release!

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