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

chore: bump kafka-manager version #562

Merged
merged 1 commit into from
Mar 18, 2019
Merged

chore: bump kafka-manager version #562

merged 1 commit into from
Mar 18, 2019

Conversation

fabriziofortino
Copy link
Contributor

Signed-off-by: Fabrizio Fortino [email protected]

What does this PR do, and why do we need it?
bump kafka-manager image to version 1.3.3.23

Which issue does this PR fix?
Adds support for kafka 2.1.1, fixes several issues

fixes #

Special notes for your reviewers:

@ghost
Copy link

ghost commented Mar 16, 2019

There were the following issues with this Pull Request

  • Commit: 4518833
    • ✖ message may not be empty
    • ✖ type may not be empty

You may need to change the commit messages to comply with the repository contributing guidelines.


🤖 This comment was generated by commitlint[bot]. Please report issues here.

Happy coding!

@fabriziofortino fabriziofortino changed the title kafka-manager: bump image version chore: bump kafka-manager version Mar 16, 2019
Signed-off-by: Fabrizio Fortino <[email protected]>
@ssalaues
Copy link
Contributor

@fabriziofortino thank you for the pr! Looks good and I will merge this into a trusted branch that we can run our CI against

@ssalaues ssalaues changed the base branch from development/1.1 to ft/ZENKO-1596-bump-kafka-manager March 18, 2019 18:32
@ssalaues ssalaues merged commit d855766 into scality:ft/ZENKO-1596-bump-kafka-manager Mar 18, 2019
@fabriziofortino fabriziofortino deleted the kafka-manager-1.3.3.23 branch March 26, 2019 22:59
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