Skip to content

feat: Update testnet/mainnet config#4

Merged
vukomir merged 1 commit intomainfrom
update-cloud-node
Mar 30, 2026
Merged

feat: Update testnet/mainnet config#4
vukomir merged 1 commit intomainfrom
update-cloud-node

Conversation

@vukomir
Copy link
Copy Markdown
Contributor

@vukomir vukomir commented Mar 30, 2026

  • Update testnet/mainnet config
  • removed dev environment

Copilot AI review requested due to automatic review settings March 30, 2026 14:02
@vukomir vukomir merged commit 401cfe6 into main Mar 30, 2026
3 checks passed
@vukomir vukomir deleted the update-cloud-node branch March 30, 2026 14:03
@AventusCI AventusCI mentioned this pull request Mar 30, 2026
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the bundled Docker bootstrap configuration for mainnet/testnet and removes the previously bundled dev environment to align supported deployments with mainnet/testnet only.

Changes:

  • Enable relay_chain_light_client: true in both mainnet and testnet configs.
  • Remove snapshot_url entries from relay chain config for mainnet/testnet.
  • Remove docker/config/dev.yml and update README to reflect supported ENVIRONMENT values.

Reviewed changes

Copilot reviewed 4 out of 6 changed files in this pull request and generated 1 comment.

File Description
docker/config/testnet.yml Enables relay-chain light client mode and removes relay snapshot configuration.
docker/config/mainnet.yml Enables relay-chain light client mode and removes relay snapshot configuration.
docker/config/dev.yml Removes dev environment bootstrap config.
README.md Updates documentation to remove dev from supported ENVIRONMENT values (plus minor pruning text edit).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread README.md
### Pruning

`blocks_pruning` and `state_pruning` are set in the bundled YAML per environment (for example `archive-canonical` for blocks and `256` for state on mainnet and testnet; dev uses the same block mode with `state_pruning: 256`). They are not controlled by separate container environment variables. To change pruning, use a custom configuration and adjust how you invoke the container, or extend or rebuild the image.
`blocks_pruning` and `state_pruning` are set in the bundled YAML per environment (for example `archive-canonical` for blocks and `256` for state on mainnet and testnet;). They are not controlled by separate container environment variables. To change pruning, use a custom configuration and adjust how you invoke the container, or extend or rebuild the image.
Copy link

Copilot AI Mar 30, 2026

Choose a reason for hiding this comment

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

The pruning paragraph has a stray semicolon before the closing parenthesis ("mainnet and testnet;)") which reads like a typo. Please remove the semicolon so the sentence is grammatically correct.

Suggested change
`blocks_pruning` and `state_pruning` are set in the bundled YAML per environment (for example `archive-canonical` for blocks and `256` for state on mainnet and testnet;). They are not controlled by separate container environment variables. To change pruning, use a custom configuration and adjust how you invoke the container, or extend or rebuild the image.
`blocks_pruning` and `state_pruning` are set in the bundled YAML per environment (for example `archive-canonical` for blocks and `256` for state on mainnet and testnet). They are not controlled by separate container environment variables. To change pruning, use a custom configuration and adjust how you invoke the container, or extend or rebuild the image.

Copilot uses AI. Check for mistakes.
@vukomir vukomir restored the update-cloud-node branch March 31, 2026 08:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants