[diff: ~metadata] <--- what Pulumi says is the reason for the update.

did you try running with verbose? see what the exact diff values are? I had this issue with multi region buckets too. Had to raise an issue with pulumi.

@bitter-cat-65329 Yes, tried with -v=3 and it didn’t yield any important information. It doesn’t spit out what the different metadata that is triggering the change. But every time I run “pulumi up” it replaces the domain mappings which takes about 10-15 for the certificates to reissue and get it back to normal state again.

hmm yeah might need to raise an issue with the pulumi-gcp team then