Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Jira Cloud CLI users should update their clients to Release 89.81 or newer to continue to work properly. Some result data related to users returned by the platform will be different and this will show in the CLI output data.

...

Confluence Cloud CLI users should update their clients to Release 9.01 or newer to continue to work properly. Some actions are no longer available for Confluence Cloud as Confluence Cloud has not yet provided replacement APIs for the APIs they removed. Once support is returned to Confluence Cloud, the CLI will re-enable those actions. Some result data related to users returned by the platform will be different and this will show in CLI output data. 

Jira Legacy
serverSystem JIRA
serverId729d679a-302c-339f-958b-015e107badcd
keyCSOAP-1050
 has more detailed information on this. One of the most likely impact areas is with managing space permissions (add and remove) - these actions will no longer be possible on Release 8.6 or higher.

...

Earlier this year, other Cloud platform changes were made to force the use of API tokens (in place of passwords) for Cloud API access. Earlier releases of CLI 8.x were modified to support this use. See Authentication options for more information on this topic.

...

  1. For some Confluence Cloud API removals, you may see the following if you do not have an updated CLI client:
    1. Remote error: Action disallowed. Response code: 403.
    2. Remote error: Unknown error occurred on server. Response code: 501.
  2. If you are NOT using the email address and API token for your user credentials for accessing Cloud sites (see Authentication options), you will likely receive: Remote error: User is not authorized to perform the request. Response code: 401.
  3. Even when using an API token, we have cases of 401 errors caused by older API tokens. Generate a new token and try again.

Links

...