I’m seeing the Appfire Confluence CLI (ACLI) v12.0.0 consistently fail against Confluence Cloud with a 404 error. It was working fine the previous day.
Example command:
<span>acli.sh confluence \ --server <a href="https://example.atlassian.net/" rel="noopener nofollow noreferrer" target="_blank">https://example.atlassian.net/</a> \ --user <email> --password <api-token> \ --action getPageList --space "LAB" --outputFormat 2</span>
Error:
<span>Client error: Unable to contact Confluence at url <a href="https://example.atlassian.net/wiki" rel="noopener nofollow noreferrer" target="_blank">https://example.atlassian.net/wiki</a>. Response code: 404.</span>
From verbose logs, ACLI is calling:
<span><a href="https://example.atlassian.net/wiki/rest/api/" rel="noopener nofollow noreferrer" target="_blank">https://example.atlassian.net/wiki/rest/api/</a><strong>latest</strong>/settings/systemInfo </span>
But Confluence Cloud only responds to:
<span><a href="https://example.atlassian.net/wiki/rest/api/settings/systemInfo" rel="noopener nofollow noreferrer" target="_blank">https://example.atlassian.net/wiki/rest/api/settings/systemInfo</a><br></span>
(curl with the same credentials works fine.)
So it looks like ACLI is appending /latest in the REST path, which Confluence Cloud no longer accepts ?.
Is anyone else running into this with Confluence Cloud + ACLI?