bridgecrew-perf6 / sfdx-deploy-package-folders

sfdx-deploy-package-folders

Use the sfdx-project.json package folders to force:source:deploy (each one in sequence)

• Debugging your plugin

$ npm install -g sfdx-deploy-package-folders
$ sfdx COMMAND
running command...
$ sfdx (-v|--version|version)
sfdx-deploy-package-folders/0.0.10 win32-x64 node-v16.7.0
$ sfdx --help [COMMAND]
USAGE
  $ sfdx COMMAND
...

• sfdx package:directory:deploy [-p <string>] [-r <string>] [-o <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

sfdx package:directory:deploy [-p <string>] [-r <string>] [-o <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

Deploy (sfdx force:source:deploy) package folders as described in the sfdx-project.json file, sequentially as defined in the project file

USAGE
  $ sfdx package:directory:deploy [-p <string>] [-r <string>] [-o <string>] [--json] [--loglevel 
  trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

OPTIONS
  -o, --options=options                                                             any additional parameters to pass
                                                                                    through to the deploy command

  -p, --project=project                                                             [default: sfdx-project.json] the
                                                                                    sfdx project json to use - will
                                                                                    retrieve package directories

  -r, --runpackagetests=runpackagetests                                             [default: true] determines whether
                                                                                    the package should look for test
                                                                                    folders and apex classes to run only
                                                                                    those tests, default is true

  --json                                                                            format output as json

  --loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
                                                                                    this command invocation

EXAMPLE
  sfdx package:directory:deploy --project sfdx-project.json --options "--wait 60 --checkonly"

See code: src/commands/package/directory/deploy.ts

Debugging your plugin

We recommend using the Visual Studio Code (VS Code) IDE for your plugin development. Included in the .vscode directory of this plugin is a launch.json config file, which allows you to attach a debugger to the node process when running your commands.

To debug the hello:org command:

1. Start the inspector

If you linked your plugin to the sfdx cli, call your command with the dev-suspend switch:

$ sfdx hello:org -u [email protected] --dev-suspend

Alternatively, to call your command using the bin/run script, set the NODE_OPTIONS environment variable to --inspect-brk when starting the debugger:

$ NODE_OPTIONS=--inspect-brk bin/run hello:org -u [email protected]

2. Set some breakpoints in your command code
3. Click on the Debug icon in the Activity Bar on the side of VS Code to open up the Debug view.
4. In the upper left hand corner of VS Code, verify that the "Attach to Remote" launch configuration has been chosen.
5. Hit the green play button to the left of the "Attach to Remote" launch configuration window. The debugger should now be suspended on the first line of the program.
6. Hit the green play button at the top middle of VS Code (this play button will be to the right of the play button that you clicked in step #5).
   
   Congrats, you are debugging!