import aws_s3_bucket_notification not creating 'bucket' field

[vit-stepanovs]

Terraform Version

Terraform v0.9.8

Affected Resource(s)

• aws_s3_bucket_notification

Terraform Configuration Files

resource "aws_s3_bucket_notification" "my_notification" {
  bucket = "my_bucket"

  lambda_function {
    lambda_function_arn = "${aws_lambda_function.my_lambda.arn}"
    events = ["s3:ObjectCreated:*"]
  }
}

Expected Behavior

If I have an S3 bucket notification set up in AWS already, and when I run

import aws_s3_bucket_notification.my_notification my_bucket

I expect terraform to reconcile the state with my manual config and not attempt to create a new notification resource.

Actual Behavior

When I run terraform plan, I see this:

-/+ aws_s3_bucket_notification.my_notification
bucket: "" => "my_bucket" (forces new resource)

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. terraform import aws_s3_bucket_notification.my_notification my_bucket
2. Put the above configuration into a .tf file.
3. terraform plan

Important Factoids

If I run terraform state show aws_s3_bucket_notification.my_notification, I see that the state contains 'id' field with the name of the bucket and no 'bucket' field.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!