You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CLI
Version 3.141.0
Go Version go1.23.3
Go Compiler gc
Plugins
KIND NAME VERSION
resource aws-native 1.9.0
language nodejs unknown
Host
OS gentoo
Version 2.17
Arch x86_64
This project is written in nodejs: executable='/run/user/1000/fnm_multishells/31012_1732329528924/bin/node' version='v20.7.0'
Current Stack: organization/pulumi-test-s3-import/demo
TYPE URN
pulumi:pulumi:Stack urn:pulumi:demo::pulumi-test-s3-import::pulumi:pulumi:Stack::pulumi-test-s3-import-demo
pulumi:providers:aws-native urn:pulumi:demo::pulumi-test-s3-import::pulumi:providers:aws-native::default_1_9_0
aws-native:s3:Bucket urn:pulumi:demo::pulumi-test-s3-import::aws-native:s3:Bucket::demo
Found no pending operations associated with demo
Backend
Name evil-eurasier
URL file://~
User ixti
Organizations
Token type personal
Dependencies:
NAME VERSION
typescript 5.7.2
@pulumi/aws-native 1.9.0
@pulumi/pulumi 3.141.0
@types/node 18.19.64
Pulumi locates its logs in /tmp by default
Additional context
AWS classic provider does not suffer from this, though:
import*asawsfrom"@pulumi/aws";constbucketName="<same bucket name as in previous example>";constbucket=newaws.s3.Bucket("demo",{bucket: bucketName,serverSideEncryptionConfiguration: {rule: {applyServerSideEncryptionByDefault: {sseAlgorithm: "AES256"},bucketKeyEnabled: true}}},{import: bucketName});exportconstarn=bucket.arn;
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered:
What happened?
When S3 Bucket resource imported can't be refreshed. Attempt to refresh - cause them to be marked for replacement.
Example
You can reproduce this with a simple script:
Output of
pulumi about
Additional context
AWS classic provider does not suffer from this, though:
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: