Skip to content

Decide the future of legacy Unit ingestion endpoints #269

Description

@jenul-ferdinand

What

Decide whether to replace the v1 Unit create, bulk-create, update, and delete endpoints with a v2 ingestion workflow or remove them.

Why

These routes provide the only data-ingestion path, but the scrapers do not call them and no v2 replacement exists.

Area

  • backend

Parent tracking issue

Notes or constraints

  • Identify the intended operational owner before choosing a v2 design.
  • Preserve a supported ingestion path before deleting routes.
  • Remove v1 routes and tests only after the replacement works.

Done when

  • Unit ingestion has a supported v2 workflow or the legacy endpoints are removed.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

backendenhancementNew feature or requestpriority: lowNice to have. Do when higher priorities are done.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions