Revert "Add archival mode to conduit (#18)"

[hsoerensen]

This reverts commit 7fb9656.

Summary by CodeRabbit

• New Features

  • Streamlined configuration across betanet, mainnet, and testnet environments, focusing on essential parameters.
  • Retained EnableFollowMode functionality, ensuring network state tracking remains active.

• Bug Fixes

  • Removed redundant and potentially confusing configuration settings, reducing complexity and the risk of misconfiguration.

These changes aim to enhance usability and maintainability while simplifying the operational model.

[coderabbitai]

Walkthrough

The pull request introduces significant changes to the configuration files for the betanet, mainnet, and testnet environments. It primarily focuses on the removal of numerous configuration parameters, streamlining the configuration process. The EndpointAddress remains unchanged across all environments, while the EnableFollowMode setting is retained, indicating that follow mode functionality is still active. Overall, the changes reflect a shift towards a more minimalistic configuration approach.

Changes

File Path	Change Summary
configuration/betanet/conduit/config.json	Removed multiple configuration parameters related to service enabling, logging, and operational limits. Retained EndpointAddress and EnableFollowMode.
configuration/mainnet/conduit/config.json	Removed several configuration options similar to those in the betanet configuration. Retained EndpointAddress and EnableFollowMode.
configuration/testnet/conduit/config.json	Similar removals of configuration parameters as in the previous files, retaining EndpointAddress and EnableFollowMode.

Possibly related PRs

• Add archival mode to conduit #18: The changes in this PR involve the addition of several configuration parameters, including Archival, EnableGossipService, and others, which are directly related to the configuration file modifications in the main PR that involve the removal of similar parameters.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between 7fb9656 and a445f22.

Files selected for processing (3)

• configuration/betanet/conduit/config.json (1 hunks)
• configuration/mainnet/conduit/config.json (1 hunks)
• configuration/testnet/conduit/config.json (1 hunks)

Additional comments not posted (6)

configuration/testnet/conduit/config.json (2)

3-3: LGTM!

The EndpointAddress configuration parameter is unchanged, ensuring that the service continues to listen on 0.0.0.0:8080 for incoming connections.

---

7-7: LGTM!

The EnableFollowMode configuration parameter is retained, ensuring that the follow mode functionality remains active in the service.

configuration/betanet/conduit/config.json (2)

3-3: LGTM!

The EndpointAddress configuration is unchanged and looks good. The service will continue to listen on all network interfaces on port 8080.

---

7-7: LGTM!

The EnableFollowMode configuration is retained and set to true, indicating that the follow mode functionality is still active. This looks good.

configuration/mainnet/conduit/config.json (2)

3-3: LGTM!

The EndpointAddress setting is unchanged, indicating that the service will continue to listen on all available network interfaces on port 8080. This is a standard configuration for network services.

---

7-7: Follow mode remains enabled.

The EnableFollowMode setting is retained with a value of true, indicating that the node will continue to operate in follow mode. In this mode, the node synchronizes its state with the network by following the blocks produced by other nodes, rather than participating in block production itself.

This configuration is suitable for nodes that do not need to actively participate in consensus but still require an up-to-date view of the network state. It can help reduce resource consumption and simplify node management.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai generate interesting stats about this repository and render them as a table.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.