Accepting because according to your test plan, it worked. It should work as long as aws-cli-v2 is used because it supports AWS_DEFAULT_REGION.

Nice, this logic makes sense to me. I'm wondering, why lock() and unlock() are undocumented in MMKV...

As far as I have context, this makes sense!

In D12926#366075, @ashoat wrote:

I think we'll need to update the two handler components here to look at the newly-returned reservedUserIdentities property, but my impression is that this will be handled by @inka in a later diff

Rename to reservedUserIdentifiers

Rename to reserved_user_identifiers

Rename to reserved_user_identifiers

Rename to reserved_user_identifiers

General question:
What's the advantage of sops-encrypting new .env files instead of reusing our sops_file resource for secrets.json, having webapp-specific config inside it, and then doing

webapp_environment_vars = merge(local.secrets.webapp_secrets,  { ... })

?

In what situations are we going to keep using the old SetDeviceTokenWithoutPlatform?

Generally okay, personally I'd organize it a bit differently but that doesn't matter

Thanks

This can be simplified and a bit more stable

I'm lacking too much context here

In D12900#365033, @varun wrote:

now that we supply platform details as metadata, should we be sending the device type in the key upload at all? seems like we should just remove it? cc @bartek

Neat! 😄 I'm not a React/UI expert so resigning, but I'm glad my gist helped.

Nice! The code structure looks neat!
In the future we can do a similar thing to our ECS services - modules can help avoid lots of duplication.

Rebase

Rebase

Add TagAwareDeserialize to the struct. This should fix CI