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.

Pulumi Community

Hey Richard, can you share your code? I just tested this with setting `content` in-line in my `gcp.storage.BucketObject` and when I change the content value, Pulumi detects this and modifies the content of the file in the google bucket.

hey <@UDEJ1F5SQ>, I should have add that I use the `source` param, not the `content` one

so my path for `source` is the same, but the file content/md5 is definitely not

Can you share the code snippet where you're creating the `gcp.storage.BucketObject`? I'm not seeing what you describe (but am seeing something different), so want to make sure I'm using it the same way you are.

sure :
```
    args.objects.forEach(object =&gt; {
      const assetName = path.basename(object, path.extname(object))
      new gcp.storage.BucketObject(
        `${name}-${assetName}`,
        {
          bucket: this.bucket.name,
          name: path.basename(object),
          source: object,
        },
        { 
          parent: this,
          dependsOn: this.bucket,
        },
      )
    })
```

where :
- `args.objects` is an array of absolute path of files on the local filesystem
- we are in the constructor of a `pulumi.ComponentResource` extended class

and giving the first object creation works fine, only a change in the file is basically invisible (no error nor update reported)

Hmm, yea, just seems like a bug. Do you mind opening an issue at <https://github.com/pulumi/pulumi-gcp>?

sure, thanks for your help, I’ll open an issue

done : <https://github.com/pulumi/pulumi-gcp/issues/87>