-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Update / rename lifecycle events of deploy plugin #1577
Comments
Imho we should do that in the next beta release, so its all prepared before the full release. Should be easy to do anyway. |
Yep. Good idea. Maybe we should also evaluate other providers before doing that... |
Imho that would be a lot of guesswork as we don't really know where providers are going and what is necessary. If we take the current lifecycle events and make them a bit more generic maybe we should be in a good place imho. |
This are the lifecycle events we currently have:
IMHO we can keep most of them. Anyway here are my proposals for name changes:
/cc @flomotlik @eahefnawy |
looks good @pmuens . If you could create a PR that can go out |
Done with #1824 |
The
lifecycleEvents
of thedeploy
plugins should be renamed to be less specific but more broadly defined so that the naming will "work" for all providers.The text was updated successfully, but these errors were encountered: