Back to all reviewers

Synchronize environment configurations

juspay/hyperswitch
Based on 6 comments
Toml

When making configuration changes, ensure all relevant environment files are updated consistently to prevent environment-specific inconsistencies and deployment issues.

Configurations Toml

Reviewer Prompt

When making configuration changes, ensure all relevant environment files are updated consistently to prevent environment-specific inconsistencies and deployment issues.

Configuration changes should be propagated across all applicable files including:

  • Development, sandbox, and production environment files
  • Docker compose configurations
  • Example and template configuration files
  • Environment-specific deployment configurations

Example of proper synchronization:

# If adding a new connector configuration in development.toml:
[newconnector]
base_url = "https://api-test.example.com/"

# Also update in:
# - sandbox.toml
# - production.toml (with production URL)
# - docker_compose.toml
# - config.example.toml (with documentation comments)

Always verify that configuration keys, formatting, and documentation comments remain consistent across all environment files. Pay special attention to URL formatting (trailing slashes), time unit specifications in comments, and naming conventions to maintain uniformity across environments.

6
Comments Analyzed
Toml
Primary Language
Configurations
Category

Source Discussions