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

• Boomi Atomsphere API token to be generated link

• 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.

• templates/azure-pipelines has yaml templates used to create Azure pipelines

• templates/configuration has json templates used to trigger Boomi jobs using a metadata file, configuration as code.

• Check this link to create the authToken link

    $ # 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 Component stuff -> This is where the component xmls will be stored
    $ export gitComponentRepoURL=""
    $ export gitComponentUserName=""
    $ export gitComponentUserEmail=""
    $ export gitComponentRepoName="BoomiComponents" # Top level folder of the GIT REPO
    $ export gitComponentOption="CLONE" # This clones the repo; else default is to create a release tag. Check gitPush.sh file
    $ export gitComponentCommitPath="/tree/master/" # For Azure Repos use this "?version=GBmaster&path=" this is used in code review report to construct the path
    $ export gitCLIRepoName="BoomiCLI" # Name of this repo in CLI this will be used in AzureReleasePipeline task
    $ export gitReleaseRepoName="BoomiRelease" # Name of the Release Repo will be used in AzureReleasePipeline task
    
    # 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.
    $ export SLEEP_TIMER=0.2 # Delays curl request to the platform to set the rate under 5 requests/second
  

    $ source bin/exports.sh
    $ source bin/publishAtom.sh > index.html

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

Boomi platform APIs support updating partial or full environment extensions. There are two CLI functions built in to support environment extensions.

1. The Create/Deploy Package CLIs scans the component XML to create the JSON required to call the update extension function. The developer needs to review the JSON and update the extensions values. The extension values can be passed as clear string or derived strings. If looking up extension from an external entity like SecretManager this has to be address in the common.sh#getValueFrom function. In this version the extension JSON is only created for Connection & Dynamic Process Properties extended by the Process, more types will be supported in future release.

2. The extension JSON generated in the previous step can be used to updateExtension.sh CLI. The updateExtension CLI supports all extension types, the get Environment Extension can also be used (here https://help.boomi.com/bundle/integration/page/int-Environment_extensions_object.html) to generate the extension JSON. When using valueFrom attribute to update secret or other variables review the common.sh | getValueFrom function to ensure it meets your need.

The following scripts publish html reports

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
• set the export VERBOSE="true" to see DEBUG messages 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.