The CLI utility wraps calls to Boomi Atomsphere APIs. Handles input and output JSON files and performance orchestration for deploying and managing Boomi runtimes, components and metadata required for CI/CD.

• The CLI utility currently runs on any Unix OS and invokes BASH shell scripts

• On Windows this has been tested with Windows Subsystem for Linux

• The CLI utility requires jq - JSON Query interpreter installed

• The CLI requires xmllit interpreter

  ## Using yum 
  $ yum install -y jq 
  $ yum install -y libxml2
  
  ## Using apt
  $ apt-get install -y jq 
  $ apt-get install libxml2-utils
  

Clone the scripts folder on to a Unix Machine. The scripts folder contains the following directories.

$ git clone https://github.com/OfficialBoomi/boomicicd-cli.git
$ cd boomicicd-cli/cli/scripts

• bin has the bash scripts for CLI

• conf has configuration files for Molecule installation

• json has json templates used in the Atomsphere API calls.

    $ # Set the following variables before the scripts are invoked. 
    $ Or Update in the bin/exports.sh and run source bin/exports
    $ source bin/exports.sh 
    
    $ # Get values from user or parameter store
    $ # The following credentials can be stored in parameter store and retrieved dynamically
    $ # Example to retrieve form an AWS store "$(aws ssm get-parameter --region xx --with-decryption --output text --query Parameter.Value --name /Parameter.name)
    
    $ SCRIPTS_HOME='/pathto/scripts'
    $ cd $SCRIPTS_HOME
    $ export accountId=company_account_uuid
    $ export [email protected]:aP1k3y02-mob1-b00M-M0b1-at0msph3r3aa
    $ export h1="Content-Type: application/json"
    $ export h2="Accept: application/json"
    $ export baseURL=https://api.boomi.com/api/rest/v1/$accountId
    $ export WORKSPACE=`pwd`
           
    # Git stuff
    $ export gitRepoURL=""
    $ export gitUserName=""
    $ export gitUserEmail=""
    $ export gitRepoName="boomi-components" # Top level folder of the GIT REPO
    $ export gitOption="CLONE" # This clones the repo; else default is to create a release tag. Check gitPush.sh file
    
    # Sonar stuff
    $ export SONAR_HOST=""  # If sonar scanner is installed locally then will use the local sonar scanner. Check the sonarScanner.sh
    $ export sonarHostURL=""
    $ export sonarHostToken=""
    $ export sonarProjectKey="BoomiSonar"
    $ export sonarRulesFile="conf/BoomiSonarRules.xml"
    $ export VERBOSE="false" # Bash verbose output; set to true only for testing, will slow execution.
    $ export SLEEP_TIMER=0.2 # Delays curl request to the platform to set the rate under 5 requests/second
  

    $ source bin/publishAtom.sh > index.html

The followings script/ calls a single API. Arguments in italics are optional

The following scripts publish html reports

• The following scripts installs Boomi runtimes (local to the script location).
• Before running the script set the tokenId variable by running the installerToke.sh CLI script.

The CLI framework is built around the functions in the common.sh

• If a script fails to run, it will print the ERROR_MESSAGE and exit with an ERROR_CODE i.e. $? > 0
• Check the $WORKSPACE/tmp.json for the input.json
• Check the $WORKSPACE/out.json for the out.json
• Call the API manually using curl -s -X POST -u $authToken -H "${h1}" -H "${h2}" $URL -d@"${WORKSPACE}"/tmp.json > "${WORKSPACE}"/out.json

This image is not supported at this time. Please leave your comments at https://community.boomi.com/s/group/0F91W0000008r5WSAQ/devops-boomi