Macros
Add-on Example
No Format |
---|
{run:titleRun=Add labels|replace=space:zcli,labels:test} {cli:profile=confluence|datasource=confluenceDS} --action runFromSql --continue @DATA: select '--action addLabels --labels "$labels" --space $space --title "' || title || '"' from content where spaceid in (select spaceid from spaces where spacekey = '$space') {cli} {run} |
CLI Documentation Links
Csv | ||
---|---|---|
| ||
Product, Reference, Examples Atlassian, [ACLI:] Confluence, [Confluence|CSOAP:Reference], [Confluence|CSOAP:Examples] JIRAJira, [JIRAJira|JCLI:Reference], [JIRAJira|JCLI:Examples] Bamboo, [Bamboo|BCLI:Reference], [Bamboo|BCLI:Examples] StashBitbucket, [StashBitbucket|SCLI:Reference], [StashBitbucket|SCLI:Examples] Crucible, [Crucible|CRUCLI:Reference], [Crucible|CRUCLI:Examples] FishEye, [FishEye|FCLI:Reference], [FishEye|FCLI:Examples] |
Tip | ||
---|---|---|
| ||
Any server instance supported by the Atlassian CLI can be accessed for running actions depending on having valid user credentials for the actions requested. This is the same as running the actions from a command line. |
Info | ||
---|---|---|
| ||
The logged in Confluence user's password is NOT available for CLI actions. A valid password is required either provided directly or via profile support. |
Profiles
Profiles allow administrators to save commonly used parameter sets for easy maintenance. This is especially important for accessing servers including server addresses, user ids, and passwords. Furthermore, by putting user ids and passwords in profiles, the password cannot be seen by normal users, only administrators that have access to add-on configuration can view the configuration.
User's should consult with their Confluence administrator on definition and usage. Administrators should view Profiles and Security for more information.