How do I ignore certain update that cann't be updated in pulumi? also I think this is a bug in

aws:redshiftserverless/namespace:Namespace:

~ aws:redshiftserverless/namespace:Namespace: (update)
        [id=ingestion-dev-us-west-2]
        [urn=urn:pulumi:backend.dev::backend::aws:redshiftserverless/namespace:Namespace::redshift-Namespace-dev-us-west-2]
        [provider=urn:pulumi:backend.dev::backend::pulumi:providers:aws::dev/network/provider::***]
      ~ iamRoles: [
          ~ [0]: "IamRole(applyStatus=in-sync, iamRoleArn=arn:aws:iam::***:role/redshift-dev-us-west-2-s3-access-role-c4e1095)" => "arn:aws:iam::***:role/redshift-dev-us-west-2-s3-access-role-c4e1095"
        ]
    ~ aws-native:docdbelastic:Cluster: (update) 🔓
        [id=arn:aws:docdb-elastic:us-west-2:***:cluster/61b9e661-d249-4994-81a8-0dba80182c45]
        [urn=urn:pulumi:backend.dev::backend::aws-native:docdbelastic:Cluster::documentdb-dev-us-west-2]
        [provider=urn:pulumi:backend.dev::backend::pulumi:providers:aws-native::dev/us-west-2/network/provider::093c5e34-b80c-4df0-b808-f6eaa4133a3d]
      + adminUserPassword: "***"
      - kmsKeyId         : "AWS_OWNED_KMS_KEY"
      ~ subnetIds        : [
          ~ [1]: "subnet-07af7d63c689725da" => "subnet-02d3aeda4ce2c0905"
          ~ [2]: "subnet-02d3aeda4ce2c0905" => "subnet-07af7d63c689725da"
        ]

If you think it’s a bug, could you file an issue at https://github.com/pulumi/pulumi-aws/issues, ideally with a Pulumi program to reproduce it? Thank you!