search

apache / infrastructure-actions

Apache infrastructure
https://infrastructure.apache.org/
1 stars 3 forks source link

Use the plugins that are already available to the action #22

Closed sebbASF closed 5 months ago

sebbASF commented 5 months ago

When an action is used, its code is loaded onto the host, and is available for use by the action. This means that an action can directly use scripts and data files, for example the plugins. There is no need to fetch the files.

Instead of using fetch_plugins.py to overwrite the site plugins directory, the new plugin_paths.py script is used to generate a suitable override value for PLUGIN_PATHS which is passed as a CLI argument to Pelican.

gstein commented 5 months ago

Very cool! Dramatic change/simplify

sebbASF commented 5 months ago

Glad you like it.

BTW, I found out that the 'use:' command imports the whole actions repo into the container. I thought it might do a sparse import of the pelican subtree (or even just copy action.yml).

Also, I'm working on some test cases; these will go into separate branches to avoid cluttering the action.

sebbASF commented 5 months ago

This branch now contains a workflow to show that the action is working OK.

It builds the testsite branch twice and checks that the output branch can be created, the site built, and the site rebuilt and updated.