We're setting up an environment in Confluence to document our product. Part of this documentation is written in Confluence, for which Versions seems to work well.
The other part of our documentation, in a different space, is generated from our source code, and then pushed to Confluence using the REST APIs (https://docs.atlassian.com/atlassian-confluence/REST/latest-server/). This yields several several problems.
Could you elaborate on to which extend you support or augment REST calls for
- Creating new versioned documents through REST
- Bumping an existing document to the next Version through REST
- Editing and bumping an existing document to the next Version through REST
- Removing a document from a specific Version through REST
I've tried finding Properties for the Versioned pages that I could potentially play with, but I haven't found any. I've tried pushing update to pages according to a specific naming convention (PUT to a page called ".test v1"), but making a change without version bumping is not really a usecase. I've tried creating new pages called ".test v2" but this did not work at all.
It may be valuable to know that
- Our versioning is semver
- I'm fine with creating a new Version before pushing my generated documents to Confluence
- Each generated document will always have the same title for all versions
I'm looking forward to your reply, as basically the entire suitability of Confluence hinges on being able to review different versions of a document/page intuitively, and the generated pages form most of our docs.
Please sign in to leave a comment.