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

[Custom Processors] Add variant starting_version field to config for when a version is already in the DB #219

Open
banool opened this issue Dec 14, 2023 · 0 comments
Labels
custom-processors Issues relating to the Custom Processors

Comments

@banool
Copy link
Collaborator

banool commented Dec 14, 2023

Description

Currently we have only one starting_version field. This field applies unconditionally, even if there is a version in the DB. This means if the user wants to start from the version in the DB if present, but otherwise start from a given version, there is no way for them to do that without a tricky order of starts and stops with adding and removing starting_version from the config.

We should have two fields (more concise naming TBD):

  • starting_version_if_nothing_in_db: If given, start from this version if nothing is in the DB.
  • starting_version_no_matter_what: Start from this version even if there is something in DB.
@banool banool added the custom-processors Issues relating to the Custom Processors label Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
custom-processors Issues relating to the Custom Processors
Projects
None yet
Development

No branches or pull requests

1 participant