Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: aws_appflow_flow perpetual diff when using task_type with value Map_all #35992

Closed
johnsonaj opened this issue Feb 27, 2024 · 3 comments · Fixed by #35993
Closed

[Bug]: aws_appflow_flow perpetual diff when using task_type with value Map_all #35992

johnsonaj opened this issue Feb 27, 2024 · 3 comments · Fixed by #35993
Assignees
Labels
bug Addresses a defect in current functionality. service/appflow Issues and PRs that pertain to the appflow service.
Milestone

Comments

@johnsonaj
Copy link
Contributor

Terraform Core Version

1.7.4

AWS Provider Version

5.38.0

Affected Resource(s)

  • aws_appflow_flow

Expected Behavior

Flow task should be able to use task_type with value Map_all without having a continuous diff on updates.

Actual Behavior

Using task_type with value Map_all produces a continuous diff when no changes are made

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

resource "aws_appflow_flow" "test" {
  name = local.name

  source_flow_config {
    connector_type = "S3"
    source_connector_properties {
      s3 {
        bucket_name   = aws_s3_bucket_policy.test_source.bucket
        bucket_prefix = "flow"
      }
    }
  }

  destination_flow_config {
    connector_type = "S3"
    destination_connector_properties {
      s3 {
        bucket_name = aws_s3_bucket_policy.test_destination.bucket

        s3_output_format_config {
          prefix_config {
            prefix_type = "PATH"
          }
        }
      }
    }
  }

  task {
    source_fields     = [""]
    task_type         = "Map_all"

    connector_operator {
      s3 = "NO_OP"
    }
  }

  trigger_config {
    trigger_type = "Scheduled"

    trigger_properties {
      scheduled {
        data_pull_mode      = "Incremental"
        schedule_expression = "rate(3hours)"
      }
    }
  }
}

Steps to Reproduce

  • terraform apply
  • terraform plan

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

@johnsonaj johnsonaj added the bug Addresses a defect in current functionality. label Feb 27, 2024
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added the service/appflow Issues and PRs that pertain to the appflow service. label Feb 27, 2024
@johnsonaj johnsonaj self-assigned this Feb 27, 2024
@terraform-aws-provider terraform-aws-provider bot added the prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. label Feb 27, 2024
@github-actions github-actions bot added this to the v5.39.0 milestone Feb 28, 2024
@github-actions github-actions bot removed the prioritized Part of the maintainer teams immediate focus. To be addressed within the current quarter. label Mar 1, 2024
Copy link

github-actions bot commented Mar 1, 2024

This functionality has been released in v5.39.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 31, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. service/appflow Issues and PRs that pertain to the appflow service.
Projects
None yet
1 participant