Skip to content

consolidate: allow using existing manifest as a cache #46

@ES-Alexander

Description

@ES-Alexander

Consolidation already takes quite a while, and it's generally unlikely that existing tags will have changed labels or a changed structure. The default behaviour should be to use the existing manifest file as a cache, and only fetch data for new tags, with the option to instead do a clean/full refresh and generate the entire file from scratch.

Something like a --cache command-line argument could be useful, where

  • if unspecified it uses the latest online manifest
  • if "none" it does a full refresh
  • if given a URL it tries to fetch it and use it, erroring out on failure to fetch
  • if given a local filename it tries to read it and use it, erroring out on failure to read

This should save a bunch of consolidation time, and also reduce unnecessary API usage.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions