Skip to content

Make the piper binary location an input parameter #206

@blackhatcrazy

Description

@blackhatcrazy

Currently the piper binary is downloaded to the fixed location ${process.cwd()}/${version}/${piperBinaryName} as seen here.

This causes problems when using this action in combination with act to run a piper-step locally.

Please allow for an alternative path configuration input for the action.

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