-
Notifications
You must be signed in to change notification settings - Fork 60
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: deprecating pubsub topic #2997
Conversation
This PR may contain changes to configuration options of one of the apps. If you are introducing a breaking change (i.e. the set of options in latest release would no longer be applicable) make sure the original option is preserved with a deprecation note for 2 following releases before it is actually removed. Please also make sure the label |
You can find the image built from this PR at
Built from 281af5b |
471bb6d
to
3f92ea7
Compare
Didn't change the terminology in the |
If that ok I will pull after next week! |
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 Nice work!
Left some suggestions.
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! Thanks for it! 💯
Just added a few minor comments that I hope you find useful
desc: | ||
"Deprecated. Default pubsub topic to subscribe to. Argument may be repeated.", |
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.
Let's create a release milestone and take note of the final deprecation. Maybe in v0.34.0
?
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.
We have #2806 open, just changed the milestone to v0.34.0
Maybe we shouldn't close this issue after this PR? or create a new one? Any of them works for me
086710f
to
0e869d5
Compare
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.
Nice, as config was confusing otherwise
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.
Generally agree with this direction. The concept of pubsub topic remains useful within the wire protocols itself as it matches more closely what is modelled in libp2p.
e65c4a5
to
dbfdda7
Compare
dbfdda7
to
c6e7332
Compare
Description
Deprecating the
pubsub-topic
CLI config in favor ofcluster-id
,shards
and a new config itemnetwork-shards
stating the amount of shards in the givencluster-id
for autosharding purposesThe word
pubsubTopic
in our codebase will refer solely to the string representation ofclusterId
+shard
that we use in thelibp2p
layer.Changes
RelayShard
type instead of pubsub topic strings in Waku's higher layersnetwork-shards
configuration item for autoshardingnetwork-shards
if not configuredIssue
closes #2806