Issue creating custom attributes/modifying default attributes

[atzawada]

Hello,

I am trying to create a user pool via the AWS CLI with some custom attributes. My custom attribute JSON looks like this:

...
"Schema": [
        {
            "Name": "sub",
            "AttributeDataType": "String",
            "DeveloperOnlyAttribute": true,
            "Mutable": false,
            "Required": false,
            "StringAttributeConstraints": {
              "MinLength": "1",
              "MaxLength": "100"
            }
          },
        {
            "Name": "userId",
            "AttributeDataType": "String",
            "DeveloperOnlyAttribute": false,
            "Mutable": true,
            "Required": false,
            "StringAttributeConstraints": {
                "MinLength": "0",
                "MaxLength": "100"
            }
        },
        {
            "Name": "userType",
            "AttributeDataType": "String",
            "DeveloperOnlyAttribute": false,
            "Mutable": true,
            "Required": false,
            "StringAttributeConstraints": {
                "MinLength": "0",
                "MaxLength": "100"
            }
        }
    ]
...

When I run

aws --endpoint http://localhost:9229 cognito-idp create-user-pool --pool-name my-user-pool --cli-input-json="$USER_POOL_JSON"

The default "sub" attribute is untouched and the custom attrs are not present. I also tried the custom attrs with the prefix custom: but this did not work as well. I tried tracing down the source of the issue but couldn't figure out where exactly I was going wrong. Any advice would be appreciated.

[jagregory]

Hey Andy, I’m away from my machine at the moment so I can’t dig in much now. I’ll be back in a couple of days. How are you verifying that the attributes aren’t saving? As far as I can remember, the create user pool call should just save whatever you send to it. I’m wondering if the create isn’t working or if it’s some other call which isn’t respecting the attributes? Can you see the attributes in the JSON file in .cognito/db ?

On Tue, 4 Jan 2022 at 2:21 pm, Andy Zawada ***@***.***> wrote: Hello, I am trying to create a user pool via the AWS CLI with some custom attributes. My custom attribute JSON looks like this: ... "Schema": [ { "Name": "sub", "AttributeDataType": "String", "DeveloperOnlyAttribute": true, "Mutable": false, "Required": false, "StringAttributeConstraints": { "MinLength": "1", "MaxLength": "100" } }, { "Name": "userId", "AttributeDataType": "String", "DeveloperOnlyAttribute": false, "Mutable": true, "Required": false, "StringAttributeConstraints": { "MinLength": "0", "MaxLength": "100" } }, { "Name": "userType", "AttributeDataType": "String", "DeveloperOnlyAttribute": false, "Mutable": true, "Required": false, "StringAttributeConstraints": { "MinLength": "0", "MaxLength": "100" } } ] ... When I run aws --endpoint http://localhost:9229 cognito-idp create-user-pool --pool-name my-user-pool --cli-input-json="$USER_POOL_JSON" The default "sub" attribute is untouched and the custom attrs are not present. I also tried the custom attrs with the prefix custom: but this did not work as well. I tried tracing down the source of the issue but couldn't figure out where exactly I was going wrong. Any advice would be appreciated. — Reply to this email directly, view it on GitHub <#93>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAACUTARNR4UAOTZU222RSTUUJRTHANCNFSM5LGPOVBA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- James Gregory Tel: 0411619513 Website: http://jagregory.com Twitter: @jagregory <http://twitter.com/jagregory>

[atzawada]

I can tell that the attributes are not saving because when I create a user pool using aws cognito-idp create-user-pool ... The json output of the pool shows nothing has been changed from the attributes. And if I try to update the attribute via my Amplify app, the call errors claiming the attribute does not exist.

I think it might have something to do with the fact that the JSON to create the user pool calls the attributes field Schema, while the output from the AWSCLI calls the field SchemaAttributes. That could be leading to the mismatch. I haven't tried using the --schema argument on that command, I can give it a try and report back.

[atzawada]

In the .cognito/db folder, looking at the JSON for the user pool, I see Schema and SchemaAttributes. When using the --schema flag it also doesn't work.

[jagregory]

Ah, yes it’s likely the difference between the request and response formats then. If you’re feeling ambitious you could have a look at the targets/createUserPool.ts file which you should see just spreads the req object when creating the pool. Otherwise I’ll take a look when I’m back.

On Wed, 5 Jan 2022 at 3:46 pm, Andy Zawada ***@***.***> wrote: In the .cognito/db folder, looking at the JSON for the user pool, I see Schema and SchemaAttributes. When using the --schema flag it also doesn't work. — Reply to this email directly, view it on GitHub <#93 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAACUTCXJ2CU4XOZMROOVODUUPEKBANCNFSM5LGPOVBA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- James Gregory Tel: 0411619513 Website: http://jagregory.com Twitter: @jagregory <http://twitter.com/jagregory>

[atzawada]

I've been poking around in the cognitoService trying to find a quick and dirty solution that maintains the default attributes but still allows for custom values and overriding. If you want to take a peek the change here: https://github.com/atzawada/cognito-local/blob/master/src/services/cognitoService.ts#L311

There's most likely a better way to do this, but I can open a PR if you want.

[github-actions]

🎉 This issue has been resolved in version 3.13.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release
• v3.13.2

Your semantic-release bot 📦🚀

[atzawada]

I stepped away from this for a few days but thanks for a quick response!