question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add "-r, --noprompt" flag to sfdx plugins:install command

See original GitHub issue

Is your feature request related to a problem? Please describe. If I setup a Jenkins CI build and specify the “sfdx” as a custom tool, I would also want to install custom plugins that I have created to aid in the build process. Currently, there is no way to execute sfdx plugins:install foo-bar without confirming the plugin installation since it is not digitally signed. Because of this, I cannot use the Jenkins Custom Tool plugin when I need specific custom SFDX CLI plugins as well.

What are you trying to do I need a way to dynamically setup the SFDX CLI and plugins that I want to install via the Jenkins custom tool option.

Describe the solution you’d like I would like a “-r, --noprompt” flag be added to plugins:install command so that I can automate on my CI builds the installation of the plugin after the installation of the SFDX CLI itself.

Describe alternatives you’ve considered I could manually install the SFDX CLI and the plugins on the Jenkins server and not utilize the “custom tool” option, but then I would not be able to dynamically spin up slave Jenkins instances as needed.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:8 (2 by maintainers)

github_iconTop GitHub Comments

6reactions
genoudcommented, Sep 25, 2019

Hello @ImJohnMDaniel A workarround to this issue: echo y | sfdx plugins:install sfpowerkit

1reaction
mshanemccommented, Dec 4, 2020

@ImJohnMDaniel there’s two other more elegant options I’d suggest.

  1. if you’re doing other npm installs for your CI, add your plugins as a dependency and then plugins:link them from the node_modules folder (when using plugins:link you don’t get the code-signing check).
  2. add those plugins to your unsignedPluginAllowList.json. More info about that file here here: https://developer.salesforce.com/blogs/2017/10/salesforce-dx-cli-plugin-update.html

1 is probably the better option for CI because your CI may get some npm-caching benefits and more granular control of which version of the plugin you’re running.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Salesforce CLI Plug-ins
When you install a plug-in with the sfdx plugins:install command, Salesforce CLI first verifies its digital signature. If the plug-in provides a valid ......
Read more >
@salesforce/plugin-source - npm
Commands to interact with source formatted metadata. Latest version: 2.3.7, last published: 13 days ago.
Read more >
nakama-plugin-sfdx - NPM Package Overview - Socket.dev
This plugin provides commands to work with the coverage files generated ... sfdx plugins:install nakama-plugin-sfdx sfdx force:source:deploy ...
Read more >
circleci/salesforce-sfdx@2.2.0
Simple example showing how to install the Salesforce sfdx CLI with the ... Run your SFDX commands here orbs: sfdx: circleci/salesforce-sfdx@x.y version: 2.1 ......
Read more >
sfpowerkit: Documentation | Openbase
echo 'y' | sfdx plugins:install sfpowerkit ... info] logging level for this command invocation --resultasstring Use this flag to get comma separated list...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found