It’s done afterward, to cut unneeded response overhead in step 3. (5) This step could have been done along with (3).‘Sync page’ is actually every page below a pre-defined parent page and is not necessarily a sync page. (3) Response data might be limited, so the request is being performed as long as not all sync pages are retrieved.Below is the overall workflow with some comments afterward. Since there was no need for the Slackbot to react on events, it is in fact only a script executed upon being triggered. Workflow between Slackbot, Confluence, and AWS (There might be changes in the workflow when using Confluence Cloud API) Confluence Server API to retrieve and post pages.A webhook is enough for only posting messages – I changed to a bot at some point to be able to schedule messages and retrieve information about channels as well. Installed Slack App in your workspace with either a webhook or bot (bot needs to be installed in the preferenced channel and will use Slack API).AWS Signing Secret (or any other way to store your credentials) – Confluence username, password, and Slackbot token are stored here.Furthermore, there are some tutorials on how to create a serverless Slackbot if you want to make usage of commands or events. AWS Lambda (or anything else to execute code) – since the Slackbot does not need to be permanently online, this was a cost-effective way.For example, the Confluence space key, the parent page id of all sync pages, a template for sync pages or the Slack-channel name where messages will be sent to.
Besides those, other configuration data is stored as variables. Listed down are the dependencies used or needed for the bot to perform its task. Let me stress that even though AWS is used, other services can be used just as well.
Create a new page with the available information in Confluence (make the best of the information available).Get all information needed from the last page (next facilitator, last sync date and next sync date).Find the latest sync page in Confluence (sync isn’t every week and other pages on the same level exist).The basic work for the bot can roughly be described as followed. Apart from this, some other adjustments need to be done which in total still results in some work and sometimes being forgotten. However, at the end of every sync page is the facilitator for the next sync mentioned – which needs to be transferred. Simply creating a new page every week would have been fairly easy, even without a Slackbot, just by creating a Confluence template.
0 kommentar(er)
