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

Backport PreInit hook support, and deprecate PreBootstrap #290

Open
wants to merge 8 commits into
base: v2
Choose a base branch
from

Conversation

masnax
Copy link
Contributor

@masnax masnax commented Nov 14, 2024

k8s-snap has requested PreInit to be included in the LTS as they are dependent on it for their LTS.

This feature clashes with the PreBootstrap hook and was meant to replace it, so instead PreBootstrap is set as deprecated, and will be replaced with a noop function if PreInit is defined by the upstream package.

…init

Signed-off-by: Max Asnaashari <[email protected]>
(cherry picked from commit 6375e4d)
Signed-off-by: Max Asnaashari <[email protected]>
(cherry picked from commit cd15984)
Signed-off-by: Max Asnaashari <[email protected]>
(cherry picked from commit 5b11527)
Signed-off-by: Max Asnaashari <[email protected]>
(cherry picked from commit 675125d)
Signed-off-by: Max Asnaashari <[email protected]>
(cherry picked from commit 4201bfa)
@masnax
Copy link
Contributor Author

masnax commented Nov 14, 2024

While setting it as deprecated is more correct, I'm a bit concerned with breaking pipelines due to linter issues which will need to be ignored or addressed if they update to v2.0.6.

Copy link
Contributor

@roosterfish roosterfish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me but I think we should rather release this in a v2.x.0 instead of a patch version as it deprecates existing features.
Whilst thinking more about this probably adding the websocket client function (as an example) would have also been a good candidate for a v2.x.0 instead of v2.0.x.

Either way I think it's not considered to be a breaking change if downstream pipelines will now produce a warning due to the deprecation of the func.
I would even say that is wanted so that they can either switch the func or proactively add an ignore statement themselves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants