has anybody tried to set

transit_encryption_mode

on an elasticache cluster? am getting this "interesting" error message that just doesnt look right:

Diagnostics:
  pulumi:pulumi:Stack (elasticache-d):
    error: Program failed with an unhandled exception:
    Traceback (most recent call last):
      File "/Users/jf/PROJS/techops/aws/elasticache/__main__.py", line 22, in <module>
        redis = aws.elasticache.ReplicationGroup(common_name,
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      File "/Users/jf/PROJS/techops/aws/venv/lib/python3.12/site-packages/pulumi_aws/elasticache/replication_group.py", line 1818, in __init__
        __self__._internal_init(resource_name, *args, **kwargs)
    TypeError: ReplicationGroup._internal_init() got an unexpected keyword argument 'transit_encryption_mode'

I had a brief look at

/Users/jf/PROJS/techops/aws/venv/lib/python3.12/site-packages/pulumi_aws/elasticache/replication_group.py

... I see

transit_encryption_enabled

in there, but no match for

transit_encryption_mode

. The terraform resource does allow for setting

transit_encryption_mode

, at least where the doc is concerned (https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/elasticache_replication_group)... nvm: I had to upgrade my

pulumi_aws

package for this to resolve