Currently aws_connect_contact_flow consists of a huge "content" JSON.
Having resources for action would give a much easier "object-oriented" approach to designing flows using Terraform.
I have designed a module to be able to have actions as pseudo-resources, but since modules can't take weakly typed inputs as variable, it is limited. Indeed, action parameters are complex objects which can't be described as variables.
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.
Description
Currently aws_connect_contact_flow consists of a huge "content" JSON.
Having resources for action would give a much easier "object-oriented" approach to designing flows using Terraform.
I have designed a module to be able to have actions as pseudo-resources, but since modules can't take weakly typed inputs as variable, it is limited. Indeed, action parameters are complex objects which can't be described as variables.
Affected Resource(s) and/or Data Source(s)
Potential Terraform Configuration
References
https://docs.aws.amazon.com/connect/latest/APIReference/flow-language-actions.html
Can't do it myself, but would be happy to discuss with whoever would implement this.
Would you like to implement a fix?
None