You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.
While building my CI with Travis I got an error while installing Salesforce DX and I just noticed that this repository is also impacted by it (build is failing at time of writing).
When running sfdx plugins:install salesforcedxthe CLI will output a blocking prompt which breaks CI:
Installing plugin salesforcedx... Checking for digital signature.
This plugin is not digitally signed and its authenticity cannot be verified. Continue installation y/n?:
I am bit surprised that this official plugin is not signed so perhaps it's a bug in the plugin build chain.
Hey @pozil - confirmed the issue. We will work on resolving this. On a side note, you shouldn't need to install salesforcedx as it is now bundled with the CLI. If you comment out that line in your CI, you can still run force commands and see the plugin version with sfdx plugins --core. The only reason to install the plugin is if you need to hardcode to a specific version.
Thx @amphro for confirming this.
I must admit that I did a copy paste from this repo so you might want to remove plugins:install salesforcedx from .travis.yml.
While building my CI with Travis I got an error while installing Salesforce DX and I just noticed that this repository is also impacted by it (build is failing at time of writing).
When running sfdx
plugins:install salesforcedx
the CLI will output a blocking prompt which breaks CI:I am bit surprised that this official plugin is not signed so perhaps it's a bug in the plugin build chain.
Here is how I fixed it based on the official DX doc:
unsignedPluginWhiteList.json
in theconfig
directory with the following content:mv config/unsignedPluginWhiteList.json $HOME/.config/sfdx/.
I hope that it helps.
The text was updated successfully, but these errors were encountered: