Skip to content

Decide the future of legacy SETU administration endpoints #268

Description

@jenul-ferdinand

What

Decide whether to build v2 SETU administration routes or remove unused v1 SETU list, aggregate, season, and write endpoints.

Why

No caller uses these v1 endpoints and no v2 replacement exists.

Area

  • backend

Parent tracking issue

Notes or constraints

  • Separate public SETU unit reads from administration behaviour.
  • Build v2 routes only for confirmed product or operational workflows.
  • Delete unused v1 routes and tests.

Done when

  • Each legacy SETU administration endpoint has a retained v2 path or is deleted.

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