Version control for Glue Workflow (orchestration) jobs and triggers?

It appears we can use the AWS CLI command get-workflow to snapshot the workflows we've created visually to JSON. I can check this into version control.

For the purposes of disaster recovery, we can use components of this output to reconstruct the individual components of the workflow using these AWS CLI Glue commands.

What's a bit frustrating is that there doesn't seem to be a way to rebuild an entire workflow in a single step from the output of the get-workflow command.

[SIDEBAR] AWS is great - I love AWS - but I get frustrated when the developers of these services do not provide the basic software lifecycle support tools that teams need to support production solutions built on these technologies. Version control and disaster recovery are severely lacking or missing completely from all of the Glue solutions we are attempting to leverage. It's embarrassing when I need to highlight to my clients all the holes and workarounds their teams need to implement outside of AWS to support and productionalize these solutions.