Skip to content
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.

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

add "always run" plugin hook #889

Open
flotter opened this issue Oct 29, 2024 · 0 comments
Open

add "always run" plugin hook #889

flotter opened this issue Oct 29, 2024 · 0 comments
Labels
Enhancement New feature or request

Comments

@flotter
Copy link

flotter commented Oct 29, 2024

What needs to get done

It would be amazing if the lifecycle manager and the plugin system can provide an optional hook for calling actions that always need to take place, irrespective if source changes occurs.

It would then allow the plugin itself to decided if some work in this category is required to be repeated or not.

Why it needs to get done

Two cases:

  1. Build time GUID generation to represent a build ID, needed to be part of metadata for a specific part/plugin.

  2. Configuration changes at the craft YAML level which needs to propagate through to some parts / plugins. For example, Pebble services config included in the craft YAML could be modified, requiring the plugin re-extract the schema and update the rootfs derived config.

@flotter flotter added the Enhancement New feature or request label Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant