???? PDF Butler deployment goes SF CLI!
You might say, why go command line? There are many reasons:
1) Automate deployment scripts
2) Integration with deployment tools (CI/CD)
3) Script setup of Sandbox or Scratch Org
4) Versioning with eg GIT repositories
5) Reduce errors and improve productivity
6) … and many more
The Butler CLI integrates directly with the Salesforce CLI.
Install it from here:Â NPM Installation
More information:Â LinkedIn post with video
Clone DocConfig:
Check the “–clone” or short “-c” parameter in the NPM guide.
More information:Â Clone via CLI
Working with GIT:
All information exported via the CLI can be stored in GIT and used for automation to upload in other Sandboxes or PROD. Below an overview how this can work:
Following command example will export from stage DEV1 in a folder “butler/docConfigs”
sf butler pb export -t <FROM ORG USERNAME MUST EXIST AS ALIAS> -i '<LONG DOCCONFIG ID>'-o 'butler/docConfigs' -s 'DEV1' -a '<PDF BUTLER USERNAME>-ADMIN:<PDF BUTLER ADMIN PWD>' -e 'https://eu1.pdfbutler.com'Following command example will import from stage QA from a folder “butler/docConfigs”
sf butler pb import -t <TO ORG USERNAME MUST EXIST AS ALIAS> -i '<LONG DOCCONFIG ID>' -f 'butler/docConfigs' -e '<PDF BUTLER USERNAME>-ADMIN:<PDF BUTLER ADMIN PWD>' -s 'QA'
