I’m following along in the tutorial, fyi, and I ha...
# general
r
I’m following along in the tutorial, fyi, and I have a few issues with the deploy step when adding a file to the bucket (https://www.pulumi.com/docs/get-started/aws/deploy-changes/):
Copy code
Previewing update (dev):
     Type                    Name          Plan       Info
     pulumi:pulumi:Stack     pulumi-t-dev             1 warning
 +   └─ aws:s3:BucketObject  index.html    create     2 warnings

Diagnostics:
  pulumi:pulumi:Stack (pulumi-t-dev):
    warning: bucket is deprecated: Use the aws_s3_object resource instead

  aws:s3:BucketObject (index.html):
    warning: urn:pulumi:dev::pulumi-t::aws:s3/bucketObject:BucketObject::index.html verification warning: Argument is deprecated
    warning: urn:pulumi:dev::pulumi-t::aws:s3/bucketObject:BucketObject::index.html verification warning: Argument is deprecated


Do you want to perform this update?  [Use arrows to move, enter to select, type to filter]
1. the object deploys fine.. but why the warning, and can we fix this? (should we be using
BucketObjectv2
?) 2. I dug a bit into the docs and found https://www.pulumi.com/registry/packages/aws/api-docs/s3/bucketobject/ (which I assume is the right doc for aws_pulumi.s3.BucketObject?). There are deprecation warnings, sure (specifically:
Deprecated: Use the aws_s3_object resource instead
), but how about giving an actual link to this “aws_s3_object resource” so we actually have more info, and hopefully know what to do?
b
@rhythmic-branch-12845 since that getting started guide has been written, the objects themselves have been changed, so we'll update them. I've created this issue here: https://github.com/pulumi/docs/issues/7362 Thanks for bringing it to our attention
r
@billowy-army-68599 thanks. Does this mean that we should not bother about the state of https://www.pulumi.com/registry/packages/aws/api-docs/s3/bucketobject/ (that my no. 2 point)?
b
the fact it's deprecated means it may be removed in future provider versions, so you can safely use it and ignore the error message if you like, but it's valid to say we should point users to the new resource with a url. I've opened this issue for that: https://github.com/pulumi/pulumi-aws/issues/1910
r
great. Thanks!