Skip to content

Not Signed workaround in a Github Action  #88

Closed as not planned
Closed as not planned

Description

@RaviVaranasi

Below is the GitHub action yml file:

    runs-on: ubuntu-latest
    steps:
      - name: Check out files
        uses: actions/checkout@v4

      - name: Install Salesforce CLI
        run: npm install -g @salesforce/cli@latest
      - name: Install Salesforce Code Analyzer Plugin
        run: sf plugins install @salesforce/sfdx-scanner@latest

      - name: Install flow scanner plugin
        run: |
          y | sf plugins:install lightning-flow-scanner

      - name: Run flow scanner
        id: run-flow-scanner
        run: sf flow:scan -d force-app/main/default/flows

Below is the output that shows that the plugin failed to install:

Run y | sf plugins:install lightning-flow-scanner
  y | sf plugins:install lightning-flow-scanner
  shell: /usr/bin/bash -e {0}
/home/runner/work/_temp/e8af88da-[3](https://github.com/invitation-homes/salesforce-blueprint/actions/runs/8318861097/job/22761347331?pr=746#step:5:3)1bb-[4](https://github.com/invitation-homes/salesforce-blueprint/actions/runs/8318861097/job/22761347331?pr=746#step:5:5)d86-9d79-80de3f84ae16.sh: line 1: y: command not found
? This plugin isn't signed by Salesforce. Only install the plugin if you trust
its creator. Do you want to continue the installation?, (y/N)

Activity

  1. nvuillam commented on Mar 17, 2024

    @nvuillam
    Contributor

    Try echo y | sf plugins:install... :)

  2. RubenHalman commented on Mar 18, 2024

    @RubenHalman
    Member

    @RaviVaranasi At the time of creation, I dont think it was possible for plugins to get signed by Salesforce yet.
    I believe it was coming or perhaps it already exists. T

    @nvuillam do you happen to know if this is now possible?

  3. nvuillam commented on Mar 18, 2024

    @nvuillam
    Contributor

    @RubenHalman a tool must be officially supported by Salesforce to be signed (even sfdx-git-delta is not ! )

    So... no choice but using echo y | ... :) (or use a tool that embeded LFS, like MegaLinter ^^ )

  4. RubenHalman commented on Mar 20, 2024

    @RubenHalman
    Member

    @RaviVaranasi For now there will be no other way then to use @nvuillam solution.

    If you do successfully implement the lightning flow scanner in github actions, will you please share your implementation with us so we can include some example in the documentation!

  5. changed the title [-]Unable to install plugin in a Github Action [/-] [+]Not Signed workaround in a Github Action [/+] on Mar 20, 2024
  6. Damecek commented on Apr 24, 2024

    @Damecek

    you should be able to bypass this using unsignedPluginWhiteList, here is more information about that.

  7. added a commit that references this issue on Nov 30, 2025
  8. locked and limited conversation to collaborators on Dec 6, 2025
  9. converted this issue into a discussion #268 on Dec 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions