This message was deleted.

sparse-intern-71089

08/06/2019, 6:30 AM

This message was deleted.

broad-dog-22463

08/06/2019, 7:20 AM

Hi @astonishing-finland-20071 Can you tell me if this is the same issue https://github.com/pulumi/pulumi-aws/issues/678

astonishing-finland-20071

08/06/2019, 7:29 AM

Well, not exactly same. My lambda trigger is post confirmation trigger. It can execute successfully but it just cause pulumi to replace user pool every time. It's more like this issue https://github.com/pulumi/pulumi/issues/2759

astonishing-finland-20071

08/06/2019, 10:33 AM

After some tests, I found it's not related to lambda triggers. It's about cognito user attributes. Even they're not changed, it still trigger pulumi to replace user pool.

broad-dog-22463

08/06/2019, 1:50 PM

If this is a separate issue can you open an issue in Pulumi-aws repo with some recreation steps?

high-morning-18773

12/12/2019, 3:44 AM

Hello is there a fix for this i notices the same issue when using python. when adding user attributes. I did specify string_attribute_constraints. There is a similar terraform issue https://github.com/terraform-providers/terraform-provider-aws/issues/3891

3 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.