Open allenmanning opened 1 year ago
Just to comment, we've hit exactly this problem - we'd love to try Quarto out in our Confluence setup, but we're using Data Center so we can't authenticate with it.
While I too am really happy to see Quarto is considering the support for the on-prem version, it's not just about authentication; what causes headache is that they have different syntax, the new editor vs the old editor (I'm not even sure if the on-prem version can use the new editor, but I bet most of these long-standing instances use the old editor...). I've been suffering from the gap during maintaining an R package to convert an R Markdown document to a Confluence page.
That is really interesting to hear about the differences between the APIs (old / new editor). Thanks for sharing that as we would then need to consider this more than just a simple switch between the low-level REST call authorization to potentially many more differences.
+1, would be nice to have since in my experience enterprise still mostly uses on-prem version of confluence and does not plan to move to cloud
Just wanted to add my support for adding this feature - My team is very excited to be able to publish to confluence via quarto but unfortunately we are also using the on-prem version.
Let me add my support for this feature, too; my employer uses only the "Data Center" product.
FWIW, if you need an extra set of eyes and hands, I am happy to contribute to code and/or test stuff.
Is there any idea when this might get picked up? Even only super-basic "push content to page id" (without the nice sub-space support that you've added) via the PUT /rest/content/{contentID}
endpoint would be super helpful already!
Is there any idea when this might get picked up?
No, thus the "Future" milestone for now. This issue (as any issues) are updated when there are new informations.
As may have noticed there are now more than 1k issues, so the team is pretty busy.
Note that if you feel up to it, you could try to make a PR to make things move forward.
We made this decision early on in the development to only focus on Confluence Cloud as Atlassian is EoLing Confluence Server in favor of Cloud.
More information on this can be found here: https://www.atlassian.com/migration/assess/journey-to-cloud.
Although Server is being EoLed, it does seem that there will be some long-standing installations of Confluence Data Center which will continue on without a Cloud migration.
We should consider this epic as adding support for Data Center. As we build up a potential case for this, we will link in issues as they are posted.
Resources