{"action":"created","issue":{"url":"https://api.github.com/repos/terraform-providers/terraform-provider-aws/issues/4392","repository_url":"https://api.github.com/repos/terraform-providers/terraform-provider-aws","labels_url":"https://api.github.com/repos/terraform-providers/terraform-provider-aws/issues/4392/labels{/name}","comments_url":"https://api.github.com/repos/terraform-providers/terraform-provider-aws/issues/4392/comments","events_url":"https://api.github.com/repos/terraform-providers/terraform-provider-aws/issues/4392/events","html_url":"https://github.com/terraform-providers/terraform-provider-aws/issues/4392","id":318813537,"node_id":"MDU6SXNzdWUzMTg4MTM1Mzc=","number":4392,"title":"Incorrect reporting of processing_configuration using AWS Provider 1.16.0","user":{"login":"si-robinson","id":20928194,"node_id":"MDQ6VXNlcjIwOTI4MTk0","avatar_url":"https://avatars2.githubusercontent.com/u/20928194?v=4","gravatar_id":"","url":"https://api.github.com/users/si-robinson","html_url":"https://github.com/si-robinson","followers_url":"https://api.github.com/users/si-robinson/followers","following_url":"https://api.github.com/users/si-robinson/following{/other_user}","gists_url":"https://api.github.com/users/si-robinson/gists{/gist_id}","starred_url":"https://api.github.com/users/si-robinson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/si-robinson/subscriptions","organizations_url":"https://api.github.com/users/si-robinson/orgs","repos_url":"https://api.github.com/users/si-robinson/repos","events_url":"https://api.github.com/users/si-robinson/events{/privacy}","received_events_url":"https://api.github.com/users/si-robinson/received_events","type":"User","site_admin":false},"labels":[{"id":620316239,"node_id":"MDU6TGFiZWw2MjAzMTYyMzk=","url":"https://api.github.com/repos/terraform-providers/terraform-provider-aws/labels/bug","name":"bug","color":"f7c6c7","default":true},{"id":801971587,"node_id":"MDU6TGFiZWw4MDE5NzE1ODc=","url":"https://api.github.com/repos/terraform-providers/terraform-provider-aws/labels/service/firehose","name":"service/firehose","color":"bfd4f2","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2018-04-30T08:11:03Z","updated_at":"2018-09-26T10:09:38Z","closed_at":null,"author_association":"NONE","body":"Hi\r\n\r\nWe have an AWS firehose that uses elasticsearch as an endpoint under terraform with AWS provider 1.10.0 that does *not* use transformation:\r\n```\r\nresource \"aws_kinesis_firehose_delivery_stream\" \"agevents-es-stream\" {\r\n  name        = \"agevents-es\"\r\n  destination = \"elasticsearch\"\r\n\r\n  s3_configuration {\r\n    role_arn           = \"${aws_iam_role.agevents-firehose-role.arn}\"\r\n    bucket_arn         = \"${aws_s3_bucket.agevents-bucket.arn}\"\r\n    buffer_size        = 5\r\n    buffer_interval    = 60\r\n    compression_format = \"GZIP\"\r\n  }\r\n\r\n  elasticsearch_configuration {\r\n    domain_arn     = \"${aws_elasticsearch_domain.events.arn}\"\r\n    role_arn       = \"${aws_iam_role.agevents-firehose-role.arn}\"\r\n    index_name     = \"${aws_elasticsearch_domain.events.domain_name}\"\r\n    type_name      = \"event\"\r\n    s3_backup_mode = \"AllDocuments\"\r\n  }\r\n}\r\n```\r\nLast week we upgraded the AWS Provider to 1.16.0 in order to use lambda transformations in a new firehose with redshift as the endpoint.  \r\nSince doing this, running `plan` always returns:\r\nelasticsearch_configuration.0.processing_configuration.#: \"1\" => \"0\"\r\nfor the original firehose.\r\nIf I apply the change and run plan again, it gives the same change it wants to make.\r\n\r\n### Terraform Version\r\n0.11.7\r\n\r\n### Affected Resource(s)\r\nelasticsearch_configuration.0.processing_configuration.#\r\n\r\n### Debug Output\r\nno errors thrown\r\n\r\n### Panic Output\r\nno panic\r\n\r\n### Expected Behavior\r\na) Running plan should not have seen that elasticsearch_configuration.0.processing_configuration.# was 1 as there was never any transformation included in the spec. \r\nb) After applying the change I would expect not to see it surfaced again by running plan.\r\n\r\n### Actual Behavior\r\nterraform indicated there was a processing_configuration when there wasn't and seems not to have updated it's state on applying the change and still sees empty config as containing a processing config.\r\n\r\n### Steps to Reproduce\r\nimport a pre-existing pipeline with no transformation into terraform using AWS provider 1.10.0.  Upgrade provider to 1.16.0.\r\nRun plan\r\nSee the above indicated.\r\nRun apply\r\nRun plan\r\nSee the above still indicated\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/terraform-providers/terraform-provider-aws/issues/comments/424660757","html_url":"https://github.com/terraform-providers/terraform-provider-aws/issues/4392#issuecomment-424660757","issue_url":"https://api.github.com/repos/terraform-providers/terraform-provider-aws/issues/4392","id":424660757,"node_id":"MDEyOklzc3VlQ29tbWVudDQyNDY2MDc1Nw==","user":{"login":"saurabh-hirani","id":485317,"node_id":"MDQ6VXNlcjQ4NTMxNw==","avatar_url":"https://avatars1.githubusercontent.com/u/485317?v=4","gravatar_id":"","url":"https://api.github.com/users/saurabh-hirani","html_url":"https://github.com/saurabh-hirani","followers_url":"https://api.github.com/users/saurabh-hirani/followers","following_url":"https://api.github.com/users/saurabh-hirani/following{/other_user}","gists_url":"https://api.github.com/users/saurabh-hirani/gists{/gist_id}","starred_url":"https://api.github.com/users/saurabh-hirani/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/saurabh-hirani/subscriptions","organizations_url":"https://api.github.com/users/saurabh-hirani/orgs","repos_url":"https://api.github.com/users/saurabh-hirani/repos","events_url":"https://api.github.com/users/saurabh-hirani/events{/privacy}","received_events_url":"https://api.github.com/users/saurabh-hirani/received_events","type":"User","site_admin":false},"created_at":"2018-09-26T10:09:38Z","updated_at":"2018-09-26T10:09:38Z","author_association":"NONE","body":"I can confirm the same. Terraform fails to store BufferIntervalInSeconds - this leads to plan showing the following output post Firehose creation:\r\n\r\n```\r\n      elasticsearch_configuration.0.processing_configuration.0.processors.0.parameters.#:                 \"2\" => \"3\"\r\n      elasticsearch_configuration.0.processing_configuration.0.processors.0.parameters.2.parameter_name:  \"\" => \"BufferIntervalInSeconds\"\r\n      elasticsearch_configuration.0.processing_configuration.0.processors.0.parameters.2.parameter_value: \"\" => \"10\"\r\n``` "}}
{"actor":{"display_login":"saurabh-hirani"}}