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

services/horizon: Add more validations for the NETWORK parameter #4988

Closed

Conversation

urvisavla
Copy link
Contributor

PR Checklist

PR Structure

  • This PR has reasonably narrow scope (if not, break it down into smaller PRs).
  • This PR avoids mixing refactoring changes with feature changes (split into two PRs
    otherwise).
  • This PR's title starts with name of package that is most changed in the PR, ex.
    services/friendbot, or all or doc if the changes are broad or impact many
    packages.

Thoroughness

  • This PR adds tests for the most critical parts of the new functionality or fixes.
  • I've updated any docs (developer docs, .md
    files, etc... affected by this change). Take a look in the docs folder for a given service,
    like this one.

Release planning

  • I've updated the relevant CHANGELOG (here for Horizon) if
    needed with deprecations, added features, breaking changes, and DB schema changes.
  • I've decided if this PR requires a new major/minor version according to
    semver, or if it's mainly a patch change. The PR is targeted at the next
    release branch if it's not a patch change.

What

Show an error message if the NETWORK parameter is provided, but ENABLE_CAPTIVE_CORE_INGESTION is set to false.

Why

The NETWORK parameter is intended to simplify captive core configuration, and it has no effect if captive-core is disabled.

Known limitations

[TODO or N/A]

@urvisavla urvisavla force-pushed the 4913/captive-core-enabled-validation branch 2 times, most recently from a861a7d to 8d86709 Compare July 28, 2023 06:27
@urvisavla urvisavla force-pushed the 4913/captive-core-enabled-validation branch from 8d86709 to b423428 Compare August 1, 2023 17:01
…ing config params when NETWORK param is used:

ENABLE_CAPTIVE_CORE_INGESTION, INGEST, NETWORK_ARCHIVE_URLS, NETWORK_PASSPHRASE, STELLAR_CORE_BINARY_PATH, and CAPTIVE_CORE_CONFIG_PATH

2. Validate that the stellar-core binary is installed and available in OS PATH
@urvisavla
Copy link
Contributor Author

After discussing with the team, we've reached a decision regarding the behavior of the individual parameters when NETWORK is specified.
CAPTIVE_CORE_CONFIG_PATH: Allowed
INGEST: Allowed
ENABLE_CAPTIVE_CORE_INGESTION: Allowed (for now)
NETWORK_ARCHIVE_URLS: Disallowed
NETWORK_PASSPHRASE: Disallowed

Closing the PR as it's no longer necessary.

@urvisavla urvisavla closed this Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants