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
The module only has one defined type, used to manage topics: kafka::broker::topic.
kafka::broker::topic
However, this code has nothing in common with kafka::broker. It is generic and could equally well be used along with brokers, producers or consumers.
kafka::broker
So this defined type should rather be named kafka::topic.
kafka::topic
Note also that the manifests/broker/topic.pp file has incorrect documentation as it contains:
manifests/broker/topic.pp
# This private class is meant to be called from `kafka::broker`.
It is not a (private) class and it is not called from kafka::broker.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
The module only has one defined type, used to manage topics:
kafka::broker::topic.However, this code has nothing in common with
kafka::broker. It is generic and could equally well be used along with brokers, producers or consumers.So this defined type should rather be named
kafka::topic.Note also that the
manifests/broker/topic.ppfile has incorrect documentation as it contains:It is not a (private) class and it is not called from
kafka::broker.The text was updated successfully, but these errors were encountered: