-
Notifications
You must be signed in to change notification settings - Fork 20
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
enabled poddisruptionbudget in case more than one broker instance is used #50
Conversation
I will have a look at the linting tomorrow morning first thing. It might have to do with my VSCode |
@ChrisJBurns can you please have another look? |
@sherifkayad Would you be able to bump the minor version as it's a new feature, I can approve and run the workflow once this is done 👍 |
@ChrisJBurns done! thanks for the feedback. |
@ChrisJBurns can you help me identify why the linting is failing? |
@sherifkayad I believe it's trailing whitespaces:
|
Can we re-check now? |
@ChrisJBurns seems to be passing after my latest push 😅 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@sherifkayad One last thing, I've only just noticed, would you be able to sign your commit? The merging is blocked until this happens. The code changes are perfect, we just need to sign the commits |
can you check now? again did a sign-off and forced pushing |
@sherifkayad Sign-off is a great addition, but I was referring to commit signing. Apologies for being a pain, but it does add a layer of security to the commits. |
…used Signed-off-by: Sherif Ayad <sherif.k.ayad@gmail.com>
@ChrisJBurns also done ;) there you go |
@sherifkayad Thanks again! All merged :) |
Sure thing! Thanks for your time reviewing as well. |
enabled poddisruptionbudget in case more than one broker instance is used