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

Plugins should be upgradable (semi)automatically #41

Open
hyfen opened this issue Mar 25, 2022 · 0 comments
Open

Plugins should be upgradable (semi)automatically #41

hyfen opened this issue Mar 25, 2022 · 0 comments
Labels
plugins Chronicle plugin system

Comments

@hyfen
Copy link
Member

hyfen commented Mar 25, 2022

If a user upgrades chronicle-etl and then uses a plugin, the plugin's gemspec might resolve an older version of chronicle-etl and then a ConflictError will be raised when attempting to load it.

This should be pretty recoverable: we check if a plugin is installed but incompatible and then call Gem.install again (todo: figure out if we have to pass an explicit version).

Also, would be useful to have a $chronicle-etl plugins:update_all command. Also maybe a $chronicle-etl plugins:cleanup for removing old versions.

@hyfen hyfen added the plugins Chronicle plugin system label Mar 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
plugins Chronicle plugin system
Projects
None yet
Development

No branches or pull requests

1 participant