Terraform latest AWS provider plugin crashing while creating AWS appflow

chandandevops · September 6, 2022, 2:26pm

terraform latest AWS provider plugin crashing while creating AWS appflow

Terraform will perform the following actions:

module.appflow.aws_appflow_flow.example will be created

resource “aws_appflow_flow” “example” {
- arn = (known after apply)
- description = “S3toSF”
- id = (known after apply)
- kms_arn = (known after apply)
- name = “S3toSF”
- tags_all = (known after apply)
- destination_flow_config {
  - connector_profile_name = “s3sfnew”
  - connector_type = “Salesforce”
  - destination_connector_properties {
    - salesforce {
      - id_field_names = [
        
        “Name”,
        ]
      - object = “orders__c”
      - write_operation_type = “UPSERT”
      - error_handling_config {
        
        bucket_name = “mskdestination-s3”
        
        bucket_prefix = “topics/orders/partition=0/”
        
        fail_on_first_destination_error = false
        }
        }
        }
        }
- source_flow_config {
  - connector_type = “S3”
  - source_connector_properties {
    - s3 {
      - bucket_name = “mskdestination-s3”
      - bucket_prefix = “topics/orders/partition=0/”
      - s3_input_format_config {
        
        s3_input_file_type = “JSON”
        }
        }
        }
        }
- task {
  - destination_field = “Name”
  - source_fields = [
    - “orderid”,
      ]
  - task_properties = {
    - “DESTINATION_DATA_TYPE” = “string”
    - “SOURCE_DATA_TYPE” = “string”
      }
  - task_type = “Map”
  - connector_operator {
    - s3 = “NO_OP”
      }
      }
- task {
  - destination_field = “address__c”
  - source_fields = [
    - “address_state”,
      ]
  - task_properties = {
    - “DESTINATION_DATA_TYPE” = “textarea”
    - “SOURCE_DATA_TYPE” = “string”
      }
  - task_type = “Map”
  - connector_operator {
    - s3 = “NO_OP”
      }
      }
- task {
  - destination_field = “itemId__c”
  - source_fields = [
    - “itemid”,
      ]
  - task_properties = {
    - “DESTINATION_DATA_TYPE” = “string”
    - “SOURCE_DATA_TYPE” = “string”
      }
  - task_type = “Map”
  - connector_operator {
    - s3 = “NO_OP”
      }
      }
- task {
  - destination_field = “orderunits__c”
  - source_fields = [
    - “orderunits”,
      ]
  - task_properties = {
    - “DESTINATION_DATA_TYPE” = “double”
    - “SOURCE_DATA_TYPE” = “string”
      }
  - task_type = “Map”
  - connector_operator {
    - s3 = “NO_OP”
      }
      }
- task {
  - source_fields = [
    - “itemid”,
    - “orderunits”,
    - “address_state”,
    - “orderid”,
      ]
  - task_type = “Filter”
  - connector_operator {
    - s3 = “PROJECTION”
      }
      }
- trigger_config {
  - trigger_type = “OnDemand”
  - trigger_properties {
    }
    }
    }

Plan: 1 to add, 0 to change, 0 to destroy.
module.appflow.aws_appflow_flow.example: Creating…
╷
│ Warning: Deprecated Resource
│
│ with module.msk.data.aws_subnet_ids.private,
│ on msk/main.tf line 7, in data “aws_subnet_ids” “private”:
│ 7: data “aws_subnet_ids” “private” {
│
│ The aws_subnet_ids data source has been deprecated and will be removed in a future version. Use the aws_subnets data source instead.
│
│ (and one more similar warning elsewhere)
╵
╷
│ Warning: Argument is deprecated
│
│ with module.msk.aws_msk_cluster.example,
│ on msk/main.tf line 76, in resource “aws_msk_cluster” “example”:
│ 76: ebs_volume_size = 10
│
│ use ‘storage_info’ argument instead
╵
╷
│ Error: Plugin did not respond
│
│ with module.appflow.aws_appflow_flow.example,
│ on appflow/main.tf line 2, in resource “aws_appflow_flow” “example”:
│ 2: resource “aws_appflow_flow” “example” {
│
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ApplyResourceChange call. The plugin logs may contain more
│ details.
╵

Stack trace from the terraform-provider-aws_v4.29.0_x5 plugin:

panic: interface conversion: interface {} is nil, not map[string]interface {}

Error: The terraform-provider-aws_v4.29.0_x5 plugin crashed!

This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin’s maintainers so that it
can be fixed. The output above should help diagnose the issue.