Summary

For over 10 years, the Confluence CLI primarily depended on Confluence's SOAP APIs. In the last couple of years, the Confluence CLI has been gradually replacing some of the SOAP APIs with newer REST APIs. This is mostly an internal implementation change with little or no external changes to the CLI. With the last few CLI 6.x releases, the pace to switch away from the remaining SOAP APIs has increased with the goal of complete elimination before CLI 7.0 is released in the summer of 2017. As this switch over proceeds, other improvements are also being made to standardize and modernize support. 

Unfortunately, Confluence REST APIs are still not complete replacements for the SOAP APIs. In those cases, we are switching over to the RPC APIs instead until the equivalent REST API becomes available from the Confluence team.

While we strive to maintain upward compatibility with functional capabilities and output (csv and other formats), there are some changes that may impact scripting that depends on other text. The following documents some of the things to watch if you have automation scripts using the CLI. 

Potential Incompatibilities

While we strive to maintain upward compatibility of the interfaces by hiding many of the differences in the underlying Confluence APIs, some incompatibilities may surface. Here's a quick list of some things to be on the lookout for especially if you have automation scripts: 

1. Text of error messages may be different. In some cases, the error message from the underlying API is surfaced directly and these have been changed by Atlassian. In other cases, we are issue our own messages and these may have changed. We also have made some improvements in this area.
2. The class of error may have changed. If your script is sensitive to the exact return value (-1 versus 3 exit codes for example) then your script may need to be updated. Some errors formerly resulting from Confluence errors (error code -3) may now be intercepted and sent from the client (error code -1) likely with some additional information.
3. login and logout actions will switch over to REST authentication instead of SOAP authentication
4. Some parameter will be deprecated. Some are no longer available with the REST APIs and others have better replacement actions based on the newer support. 
   • search related parameters will be removed in favor of the more modern and powerful cql parameter
5. removePage and removeBlog actions will require the --continue parameter to avoid failing on not found errors

Legacy Support

For a limited time only, you can use the --options legacy parameter to continue using the older support for most migrated support.

Watch This Page

Watch this page for updates as more information becomes available.