We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As today the Operator start/stop methods do not have any barrier to avoid the methods to be invoked more than once and as example, since the introduction of the PR here https://github.com/quarkiverse/quarkus-operator-sdk/blob/main/runtime/src/main/java/io/quarkiverse/operatorsdk/runtime/StartupListener.java, I've observed that my operator did invoke start twice because I also had a startup listener to implement the same functionality.
I have now fixed my code so id does not happen anymore but I feel a barrier on the start/stop methods could be useful in any case.
The text was updated successfully, but these errors were encountered:
@metacosm pr #491 may address this issues
Sorry, something went wrong.
metacosm
Successfully merging a pull request may close this issue.
As today the Operator start/stop methods do not have any barrier to avoid the methods to be invoked more than once and as example, since the introduction of the PR here https://github.com/quarkiverse/quarkus-operator-sdk/blob/main/runtime/src/main/java/io/quarkiverse/operatorsdk/runtime/StartupListener.java, I've observed that my operator did invoke start twice because I also had a startup listener to implement the same functionality.
I have now fixed my code so id does not happen anymore but I feel a barrier on the start/stop methods could be useful in any case.
The text was updated successfully, but these errors were encountered: