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: deprecating pubsub topic config #2779

Closed
wants to merge 30 commits into from

Conversation

gabrielmer
Copy link
Contributor

Description

Deprecating the pubsub-topic CLI config in favor of cluster-id, shards and a new config item network-shards stating the amount of shards in the given cluster-id for autosharding purposes

Renamed the CLI config ProtectedTopic to ProtectedShard. The idea is to avoid ambiguity so the user only has to be familiar with the terms cluster and shard.

The word pubsubTopic in our codebase will refer solely to the string representation of clusterId+shard that we use in the libp2p layer.

Copy link

github-actions bot commented Jun 5, 2024

You can find the image built from this PR at

quay.io/wakuorg/nwaku-pr:2779-rln-v2

Built from a4b768b

Copy link

github-actions bot commented Jun 5, 2024

You can find the image built from this PR at

quay.io/wakuorg/nwaku-pr:2779-rln-v1

Built from a4b768b

Copy link

github-actions bot commented Jun 5, 2024

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 release-notes is added to make sure any changes to the user interface are properly announced in changelog and release notes.

@gabrielmer gabrielmer added the release-notes Issue/PR needs to be evaluated for inclusion in release notes highlights or upgrade instructions label Jun 5, 2024
@gabrielmer gabrielmer force-pushed the chore-deprecating-named-sharding branch from 5d93874 to 65cb4f5 Compare June 10, 2024 08:06
@gabrielmer gabrielmer force-pushed the chore-deprecating-pubsub-topic-config branch from 79c89fc to d6385d6 Compare June 10, 2024 08:15
@gabrielmer gabrielmer force-pushed the chore-deprecating-named-sharding branch from 65cb4f5 to 32675a8 Compare June 10, 2024 12:32
@gabrielmer gabrielmer force-pushed the chore-deprecating-pubsub-topic-config branch from d6385d6 to 2e3dd36 Compare June 10, 2024 12:33
Copy link
Collaborator

@fryorcraken fryorcraken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

.

@gabrielmer gabrielmer force-pushed the chore-deprecating-named-sharding branch from 32675a8 to 519a119 Compare July 2, 2024 13:24
@gabrielmer gabrielmer force-pushed the chore-deprecating-named-sharding branch from 61c7815 to 4565042 Compare July 9, 2024 14:39
Base automatically changed from chore-deprecating-named-sharding to master July 9, 2024 15:36
@gabrielmer gabrielmer added E:1.2: Autosharding for autoscaling See https://github.com/waku-org/pm/issues/65 for details E:nwaku Sharding peer management and discovery and removed E:1.2: Autosharding for autoscaling See https://github.com/waku-org/pm/issues/65 for details labels Aug 21, 2024
@gabrielmer
Copy link
Contributor Author

Closing this PR as it will be replaced by #2997

@gabrielmer gabrielmer closed this Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E:nwaku Sharding peer management and discovery release-notes Issue/PR needs to be evaluated for inclusion in release notes highlights or upgrade instructions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants