I'm curious, how a good automated workflow could look like for the process of automating issues/touched file lists into a confluence page. I describe my current idea here:

Get all issues matching my request from JIRA using REST (DONE)
Get all touched files related to the matching Issues using Fisheye REST
Create a .adoc file with the content
Render it using asciidoctor-confluence to a confluence page

I'm implementing the this in python (using requests etc.) and I wonder how I could provide proper .adoc for the ruby-based asciidoctor. I'm planning to use asciidoctor for the reason it has an option to render directly to confluence using asciidocter-confluence. 
So, is there anybody who can kindly elaborate on my idea?
I did something similar - getting info from Jira and updating confluence info.
I did it in a bash script that ran on Jenkins. The script:

Got Jira info using the Jira REST API
Parsed the JSON from Jira using jq (wonderful tool)
Created/updated the confluence page using the Confluence REST API

I have not used python but the combination of bash/REST/jq was very simple. Running the script from Jenkins allowed me to run this periodically, so confluence is updated automatically every 2 weeks with the new info from Jira.
Programmatically create confluence content from jira and fisheye