| Page Properties | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
\uD83D\uDCCA Success metrics
Goal | Metric |
|---|---|
\uD83E\uDD14 Assumptions
\uD83C\uDF1F Milestones
...
\uD83D\uDDD2 Requirements
Requirement | User Story | Importance | Jira Issue | Notes | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
We would like to use FUSE for SQS registration. | Need to implement a new feature on the FUSE side for supporting SQS registration without EventBridge |
|
| As a temporal workaround we can create it manually. | ||||||||||||||
Implement Lambda webhooks handler. | Most of the events will be handled using lambdas but some of them(app installed & uninstalled) should be redirected to the SQS. |
|
| Update page relations based on the following events(confluence webhooks) on the backend side:
| ||||||||||||||
Implement ECS service. | Need to scan all Confluence pages and update link references. |
| Background job must scan all confluence pages since the last re-index date if exists and update page relations. |
\uD83C\uDFA8 New design high level architecture:
...
The idea is to perform whole Confluence content reindex for our API & data access. We need it in order to make page links accessible through a REST API.
SO, when users add page link macro our app can easily gather all needed links for a specific page.
Open Questions
Question | Answer | Date Answered |
|---|---|---|
Do we need to keep links for archived pages? | [most likely no, but…] |
Out of Scope