-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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]: An argument named "path_prefix_hierarchy" is not expected here. #34634
Labels
service/appflow
Issues and PRs that pertain to the appflow service.
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
github-actions
bot
added
the
service/appflow
Issues and PRs that pertain to the appflow service.
label
Nov 29, 2023
terraform-aws-provider
bot
added
the
needs-triage
Waiting for first response or review from a maintainer.
label
Nov 29, 2023
Duplicate of #31874 |
justinretzolk
removed
bug
Addresses a defect in current functionality.
needs-triage
Waiting for first response or review from a maintainer.
labels
Jan 19, 2024
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Core Version
1.6.5
AWS Provider Version
5.28.0
Affected Resource(s)
aws_appflow_flow
Expected Behavior
terraform plan should succeed
I'm trying to create the flow with partition settings, following the original documentation, but, unfortunetly, the resource is not functional.
Actual Behavior
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
terraform plan
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
https://docs.aws.amazon.com/cli/latest/reference/appflow/create-flow.html
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/appflow/client/create_flow.html
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: