Closed sebbASF closed 5 months ago
Note also that a site may provide its own plugins.
Rather than try to determine which shared plugins are being used, why not provide a known directory on the build host which contains all the available shared plugins, and ensure that the directory is included in the PLUGINS_PATH?
257e1056 shows how to load the pelicanconf.py and grab that value. I think we'll switch to this pattern.
The parsing does not allow for mulitple lines:
https://github.com/apache/infrastructure-actions/blob/06fa613303528411ddb4b1da8a1d028781e7b81a/build-pelican/action.yml#L49
It also assumes that plugin names will be delimited by single quotes.