Salesforce CLI allows for extensibility through plugins created by Salesforce teams, employees, and community members. Creating a plugin requires knowledge of TypeScript, Node.js, npm, and Salesforce APIs. The CLI makes it easy to generate a starter plugin template and link it for testing using commands like sfdx plugins:generate and sfdx plugins:link. The document provides references for further learning about plugins and the Salesforce CLI.

1. Salesforce DX
A closer look - Part II

2. Salesforce Engineer @
Sitetracker via BairesDev
federico.giust@icloud.com
@federicogiust
Federico Giust

3. The Salesforce CLI core plug-ins provide commands and functionality to meet common needs
that customers and partners have. But each team often has specific needs.
That’s why Salesforce CLI is extensible. Even at Salesforce, different teams have different
requirements. Salesforce teams create plug-ins, Salesforce employees create plug-ins as side
projects, and Trailblazers in the Salesforce community create and share plug-ins.
Why create plugins?
https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_plugins.meta/sfdx_cli_plugins/cli_plugins.htm

4. Knowledge & Skills
Building a Salesforce CLI plug-in requires different knowledge and skills than most Salesforce
development. Before you dive too deeply into plug-in development, familiarize yourself with these
areas.
• TypeScript (or at least JavaScript, which TypeScript transpiles to)
• Node.js
• npm (Node.js Package Manager)
• Yarn in modern JavaScript build tools
• Salesforce APIs

5. It’s very easy to start your first plugin with the generator.
sfdx plugins:generate yourPluginName
The new plug-in contains an example hello:org command. You can find the code for that command
at yourPluginName/src/commands/hello/org.ts
To run the commands in your in-development plug-in from the directory that your code lives in,
precede the commands with bin/run. Look at the --help (-h) output for the sample hello:org command.
Customize your plug-in. (This step might take a while!) To test your functionality along the way,
run:
bin/run yournamespace:yourcommand
When you’re ready (see the Tip) to test-drive your plug-in, link your in-development plug-in to
Salesforce CLI running: sfdx plugins:link
Scaffold your first plugin
https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_plugins.meta/sfdx_cli_plugins/cli_plugins.htm

6. DEMO

7. Referencias
https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_develop.htm
https://developer.salesforce.com/tools/vscode/articles/getting-started/install
http://montevideosdg.com
https://trailblazercommunitygroups.com/montevideo-uy-developers-group/
https://github.com/wadewegner/
https://marketplace.visualstudio.com/items?itemName=VignaeshRamA.sfdx-package-xml-generator
https://github.com/fedegiust/sfdx-git-deploy

8. Q&A

9. montevideosdg.com
Thank you!!!