New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make plugin configuration end-user configurable #29

Open

RobertKielty opened this issue Oct 10, 2022 · 1 comment

Assignees

Labels

area/pga enhancement

Contributor

RobertKielty commented Oct 10, 2022 •

edited

Loading

As a Project Maintainer I should be able to choose what plugins are configured on my invocation of PGA from a Github Action that I am maintaining.

Right now, the plugins.yaml file is packaged up with the ko built container pga.
Allow a Project Maintainer to inject their own plugins.yaml file (preferably from from a standard location in the project repo where the Action is running pga)

RobertKielty added enhancement area/pga labels

Contributor Author

RobertKielty commented Oct 12, 2022

/assign @RobertKielty

github-actions bot assigned RobertKielty

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment