Overview
This article provides answers to most frequently asked questions on the CLI app.
FAQs
Where exactly does this app run ?
Jira/Confluence/Bamboo/Bitbucket/Atlassian Command Line Interface (CLI) has 2 components
- CLI Connector - This is installed on the server using Universal Plug-in Manager (UPM) and provides a specific license validation REST API. It is accessible to CLI client via <base-url>/rest/org.swift.confluence.cli/latest/validatelicense.
- CLI Client - This is installed on any system (Windows, Linux, OSX) that has Java 8 or higher. The CLI client runs on this system.
CLI Client can be downloaded from Downloads - CLI Clients to the local machine where actions are run from. See the page What is the difference between CLI clients and Run CLI add-ons?
Do clients still require an instance add-on (CLI Connector) be installed ?
Yes (with some exceptions). This has not changed. The Connector add-on provides license enforcement and, in some cases, extended remote interfaces not available from the base Atlassian product.
A few clients are provided at no charge and do not require a connector. They include:
Can CLI Clients be purchased separately ?
No. CLI Clients are available for no-charge with the purchase of one or more of server or cloud add-ons.
What does an existing Run CLI Actions app customer need to do to remain properly licensed ?
Nothing if they do not use CLI Clients and only use the integrated support as part of their Atlassian product. Renew your license as usual when maintenance has expired.
If you want to use CLI Clients as well as the integrated capabilities, then an additional license is needed for the CLI Connector. This license change was effective from CLI version 6.x but only enforced when upgrading Clients to 7.0 or higher. If you are entitled to a discounted license (determined as per maintenance expiry date), contact us at license@appfire.com.
How can I evaluate the CLI app prior to purchase ?
Obtain an evaluation license for one of the Atlassian apps listed, install on the app, then download the ACLI Client distribution. See CLI Client Installation and Use for more information.
Can ACL ClientI be used to access a server that does not have the Connector app installed ?
No. ACLI Client is not licensed be used to access an Atlassian app that requires a connector app to be installed.
Can I continue to use a version of ACLI Client prior to version 7 ?
Yes. Versions prior to 7.0 can be used under the terms in effect at that time. Links are available in the Related Information section.
Do I need to purchase both the CLI and Run CLI Action apps to use both the client and the product specific functions ?
Yes. You need to purchase both the CLI and Run CLI Action apps to use both the client and the product specific functions.
If I am an official Atlassian Partner or Expert, can I get a special rate for CLI app?
Yes. Atlassian recognised partners and members of the Atlassian Experts Program can use any CLI app free of charge for development, testing, or demonstration purposes. A commercial license is required when used to provide services to customers. See Add-ons for Atlassian Experts for more details.
Are CLI apps available for Atlassian Cloud ?
Yes. CLI apps for Jira, Jira Service Desk, Confluence Cloud, etc. are available in Atlassian Cloud for purchase or trial subscription. Bitbucket Cloud is also supported by the ACLI Client and is currently available for a limited time at no charge.
Do I need a CLI license for Atlassian server that is a developer/test system ?
No, for all servers except Crucible/FishEye.
- Any Atlassian paid app automatically provides a developer license associated with your production license. Go to my.atlassian.com, expand the app, and look for a link.
- We have purposefully allowed CLI to work with developer servers where the connector is installed but do not have a license. This is to make it easier for administrators and add-on developers.
- Unfortunately, we are unable to provide same support for Crucible/FishEye at this time due to limitations in determining a developer licensed server.
How many client users can I have ?
Unlimited. Any number of users can install clients and connect to a server. The requirement is that the host must have the CLI Connector component installed with valid license.
Which server product should I choose ?
Choose the product specific Command Line Interface (CLI Connector) if you want to use a client to connect to the Atlassian product.
Choose the product specific Run CLI Actions app for integrated capabilities like JIRA workflow actions, Confluence macros, Bamboo tasks, or similar product capabilities available with these apps.
Where do I find a CLI Connector on the Marketplace ?
Each of the following product specific Command Line Interface (CLI) Marketplace entries represent respective CLI Connectors (UPM installable). The links are provided as under:
The following clients do not need a Connector:
Where do I find the CLI Client on the Marketplace ?
Atlassian Command Line Interface (CLI) provides a client distribution that contains all product specific clients. It is included at no charge with any of the CLI Connectors.
How does CLI Client access Atlassian applications ?
The CLI client uses request/response protocol built on REST API calls provided by Atlassian. It perform remote actions against your Atlassian applications.
What permissions does CLI Client require ?
Nothing specific to the app. The users standard Atlassian application permissions determine what the user can or cannot do, just like any other instance access via REST APIs or the user interface.
Our app honors the permissions provided by the host app and if the user does not have specific permission, the user will not be allowed to perform the action using CLI client.
How is a CLI Client user authenticated ?
The CLI Client authentication is different between Cloud and Server versions of Confluence. For server, authentication is based on the username and password provided when running the command from the CLI Client or distribution. For Cloud, authentication is based on the username as email Id and password as API token. For additional information on authentication, see this document.
Are there any risks, using CLI app ?
The risks in using this app are no different from performing the same operations via the Atlassian application user interface. CLI has only those capabilities that Atlassian provided API offers. That said, as with any automation tool, we encourage our customers to carefully test their CLI actions in test environments whenever possible. We also suggest using the simulate option to understand in detail what a given command does before using it in a live environment.
Can this app be misused beyond the application permission given to users ?
No. The CLI can only perform operations that the user executing CLI can do via the Atlassian application's user interface. So, while it cannot be misused, it is very powerful and so should be used with caution and testing.
What can be done, if the above happens ?
The recourse or rollback options are identical to those in the UI. Some options to consider are making backups on data that is about to be changed or making a plan to revert the changes, if needed, via the CLI. For example, if using the CLI to create new users in bulk, one should have a CLI command ready to remove or disable those users if the results are unexpected.
What do customers like in this app ?
Our customers use the CLI to automate tedious and repetitive tasks so that they can spend their time on more valuable work. Many hours are saved daily by our customers. Some operations in the Atlassian user interface that require many clicks and many screens can be performed using minimal commands.
How easy is this app to learn ?
The CLI is a very powerful tool. For example, it has over 200 actions available for Confluence. This can sometimes be a challenging learning curve until one understands consistent patterns in the commands. Once that is understood well, creating CLI commands becomes easier.
