Skip to content

Document and systematically implement tool source and tool version somewhere #3628

@MoralCode

Description

@MoralCode

tool source == Which Augur collector/task/worker inserted the data
tool version == the version of that tool

We typically only change the version when there is a significant change to its collection logic (i.e., API changes, or refactoring of collection tools).

Originally posted by @sgoggins in #3587 (comment)

If the version is only changed when significant collection changes happen to the workers, we should probably also consider giving each worker/python sub package/modular component of augur its own __metadata__ file, possibly linked to/referring to the main one so its easy to update (and then having the tool_version pull from that)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions