Release date:
Our team is thrilled to announce the latest release of Appfire Command Line Interface (CLI), version 12.0.0.
Compatibility: Refer to the Compatibility - 12.0 page.
Contents |
---|
The new archiveSpace
and restoreSpace
actions are now available for Confluence Server installations running version 8.8 or later. These actions use the API endpoints introduced in Confluence 8.8. Note that these actions are only supported on Confluence Server 8.8 or newer, as Confluence Cloud does not currently offer a public API for this functionality.
updateSpace
action for archiving spaces in Confluence 8.8+The updateSpace
action now uses the updated API endpoint when you include the --options "status = archived"
parameter to archive spaces on Confluence Data Center installations running version 8.8 or later. This update aligns with the new archiveSpace
and restoreSpace
actions introduced in this ACLI release, which also use the same API endpoint.
The shell site configuration workflow for http://monday.com sites no longer supports OAuth as an authentication option.
The Bitbucket CLI connector plugin now fully supports Bitbucket 9, ensuring complete compatibility with Platform 7. This update allows seamless integration with the latest version of Bitbucket.
The Run Jira CLI plugin now fully supports Jira 10, ensuring compatibility with Platform 7. This update enables seamless integration with the latest version of Jira.
The Jira CLI connector plugin now fully supports Jira 10, ensuring compatibility with Platform 7. This update enables smooth integration with the latest version of Jira.
The Run Confluence CLI now fully supports Confluence 9, ensuring compatibility with Platform 7. This update allows seamless integration with the latest version of Confluence.
The Confluence CLI connector plugin now fully supports Confluence 9, ensuring compatibility with Platform 7. This update enables smooth integration with the latest version of Confluence.
All run*
actions now support the --options value interactive
parameter, enabling an interactive mode. In this mode, the action automatically pauses after each action or iteration and presents a simple prompt. The prompt allows users to enter specific commands to control how ACLI proceeds.
Additionally, ACLI scripts now support a new suspend
keyword. When encountered (on its own line), the script pauses execution at that point. This feature is especially useful for debugging or performing manual operations before resuming the script.
Example usage:
./aclidev cg -a run -i "-a getClientInfo" -i "-a getServerInfo" --options interactive |
Example output:
Run: -a getClientInfo Client name: jiracloud, Client version: 12.0.0-SNAPSHOT, Build date: 2024-11-20T16:04:35, Java: Java HotSpot(TM) 64-Bit Server VM 21.0.3, OS: Mac OS X 14.4.1 Suspended. Enter [i] for info, [n] to run next, [a] to run all, [q] to quit. command> i Action . . . . . . . . . . . : -a getClientInfo Exit Code . . . . . . . . . : SUCCESS Replacement Variables . . . . : @exitCode@ . . . . . . . . : 0 command> n Run: -a getServerInfo Jira version: 1001.0.0-SNAPSHOT, build: 100277, time: 11/21/24, 8:42 AM, description: Jira, url: https://cannibal-gods.atlassian.net Suspended. Enter [i] for info, [n] to run next, [a] to run all, [q] to quit. command> a Run completed successfully. 2 actions were successful from input parameters. |
Available Commands:
i
: Displays basic information about the current runtime state, including replacement variables and their values.
n
: Runs the next action.
a
: Runs all remaining actions until the next interactive option or suspend
keyword is encountered.
q
: Exits ACLI immediately without running any further actions.
These enhancements make it easier to debug scripts, pause for manual interventions, and control execution flow interactively.
The following bugs are fixed in this release:
Previously, due to an issue with the --copysubtask
parameter when cloning issues, subtasks were copied in the order of their creation timestamps (DTS) by default, ignoring any user-defined order. The --copysubtask
parameter now correctly copies subtasks to the cloned issue while preserving their original ranking from the source issue.
An issue that caused a NoClassDefFoundError: org/bouncycastle/jce/provider/BouncyCastleProvider
error to occur when running actions. The issue was resolved by adding the missing class configuration for BouncyCastleProvider
in reflect-config.json
.
A change in the Jira API requiring products to be specified for user access caused the addUser
action to fail with the error message: "Remote error: You must specify the products that user can access." We updated the addUser
action to support this API requirement, ensuring it functions correctly.
An issue that caused the error Can't find resource for bundle java.util.PropertyResourceBundle, key error_misc_fileNotFile
. This issue occurred because a required resource key was missing in the PropertyResourceBundle
.
An issue where using RequestContentType.URL_ENCODED
caused an invalid Content-Type
header value. The URL_ENCODED
(application/url_encoded) value has been removed as a valid option for the contentType
parameter. While this value can still be used, it no longer appears as a valid choice in shell prompts and should be avoided to prevent issues.
Questions and feedback
Explore exciting features, pricing updates, reviews, and more on the Marketplace.
Stuck with something? Raise a ticket with our support team.
Do you love using our app? Let us know what you think here.
Credits
A heartfelt thank you to our valued customers! Your incredible support and feedback inspire us to improve our apps and products continually. You are the driving force behind why we create software. We appreciate your trust in Appfire Command Line Interface (CLI)!
|