gcp.storage.BucketObject does not refresh an object if using the source parameter instead of content about pulumi-gcp HOT 7 CLOSED

This definitely seems like a bug where we're accepting a string when only an Archive should be allowed. This would explain the odd diffing behavior.

from pulumi-gcp.

@joeduffy Ok, I see what you mean when looking into the method documentation.

How one is supposed to create/use an Archive in this case instead of a string then ?

Couldn't you accept a string and automatically create an Archive (whatever that is) from it under the hood to handle this simple case ?

from pulumi-gcp.

Per an internal conversation, source should be retyped to Asset rather than Archive. This should achieve the correct/expected behavior.

from pulumi-gcp.

See also pulumi/pulumi#280 which is sort of a root cause here.

from pulumi-gcp.

We should do a sweep of source properties that map to files on disk and ensure we have mapped them to Assets/Archives. It was raised recently that aws.lambda.Layer has a similar problem (we addressed this for aws.lambda.Function a long time ago). We'll also need to come up with a general strategy here on two fronts:

1. How to make the change from source: string to something: Asset
2. How to decide whether to accept Asset or Archive, and ideally how to ensure that we don't have to make this decision at all by fixing pulumi/pulumi#280.

Given how many commonly used APIs this impacts, would be great to tackle these sooner than later.

from pulumi-gcp.

This is fixed in #101, but we likely don't want to release it until after #106 is considered OK to go out, since it represents a breaking type change. Consequently, I'll move this to M22.

from pulumi-gcp.

This seems dependent on pulumi/pulumi#280, which is not currently assigned. For now I'll remove this from a milestone, though #101 should fix this when pulumi/pulumi#280 is dealt with.

from pulumi-gcp.