Terraform Core Version

1.5.0

AWS Provider Version

5.41.0

Affected Resource(s)

aws_appflow_flow

Expected Behavior

AppFlow Flow status should be configurable in the resource block.

Relating to this issue #34574: when an AppFlow Flow is pushed with trigger_type="Scheduled" it was deploying in AWS with a status of "Draft", not "Active" - requiring an additional step either through the UI or API to update the flow to a status of "Active" before the flow could be used.

Actual Behavior

A fix was subsequently implemented on #34948 addressing the original issue.

However, the merged fix appears to have no affect on the behavior - Flows are still deployed in a "Draft" state requiring additional interaction in the UI or API before the flow is useable. The documentation states that a "flow_status" attribute reference is exported, but makes no reference to this field as an argument in the resource block.

Relevant Error/Panic Output Snippet

Error: Value for unconfigurable attribute
│ 
│   with module.appflow_flows.aws_appflow_flow.flow,
│   on main.tf line 31, in resource "aws_appflow_flow" "flow":
│   31:   flow_status = "Active"
│ 
│ Can't configure a value for "flow_status": its value will be decided automatically based on the result of applying this configuration.

Terraform Configuration Files

resource "aws_appflow_flow" "flow" {
  name       = "my-appflow-name"
  flow_status = "Active"
  ...
  trigger_config {
        trigger_type="Scheduled"
        trigger_properties{
            scheduled {
                schedule_expression  = "cron(0 1 * * ? *)"
            }
        }
    }
}

Steps to Reproduce

1. Deploy resource without a status argument
2. Observe "Draft" value on the "Flow status" field in UI:
   

1. Deploy resource with flow_status = "Active" status argument
2. Observe error message:

Can't configure a value for "flow_status": its value will be decided automatically based on the result of applying this configuration.

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None