Appflow flow status

[Viriathus1]

Description

Following up on #34948. Allow flow status to be configurable in resource block for Scheduled or Event triggered flows. Main use case is to obviate the need to manually activate an AppFlow during resource creation and update.

Relations

Closes #36441

References

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-appflow-flow.html#cfn-appflow-flow-flowstatus
https://docs.aws.amazon.com/appflow/1.0/APIReference/API_StartFlow.html
https://docs.aws.amazon.com/appflow/1.0/APIReference/API_StopFlow.html

Output from Acceptance Testing

% make testacc TESTARGS='-run=TestAccAppFlowFlow_update' PKG=appflow
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.22.2 test ./internal/service/appflow/... -v -count 1 -parallel 20  -run=TestAccAppFlowFlow_update -timeout 360m
=== RUN   TestAccAppFlowFlow_update
=== PAUSE TestAccAppFlowFlow_update
=== CONT  TestAccAppFlowFlow_update
--- PASS: TestAccAppFlowFlow_update (48.00s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/appflow	55.036s

% make testacc TESTARGS='-run=TestAccAppFlowFlow_activateFlowStatus' PKG=appflow
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.22.2 test ./internal/service/appflow/... -v -count 1 -parallel 20  -run=TestAccAppFlowFlow_activateFlowStatus -timeout 360m
=== RUN   TestAccAppFlowFlow_activateFlowStatus
=== PAUSE TestAccAppFlowFlow_activateFlowStatus
=== CONT  TestAccAppFlowFlow_activateFlowStatus
--- PASS: TestAccAppFlowFlow_activateFlowStatus (37.14s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/appflow	43.912s

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull 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.

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[github-actions]

Welcome @Viriathus1 👋

It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTOR guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.

Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.

Thanks again, and welcome to the community! 😃