-
Notifications
You must be signed in to change notification settings - Fork 53
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 config #2779
Conversation
You can find the image built from this PR at
Built from a4b768b |
You can find the image built from this PR at
Built from a4b768b |
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 |
5d93874
to
65cb4f5
Compare
79c89fc
to
d6385d6
Compare
65cb4f5
to
32675a8
Compare
d6385d6
to
2e3dd36
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.
.
32675a8
to
519a119
Compare
61c7815
to
4565042
Compare
Closing this PR as it will be replaced by #2997 |
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 purposesRenamed the CLI config
ProtectedTopic
toProtectedShard
. The idea is to avoid ambiguity so the user only has to be familiar with the termscluster
andshard
.The word
pubsubTopic
in our codebase will refer solely to the string representation ofclusterId
+shard
that we use in thelibp2p
layer.