raystack / raystack/frontier

Drop the deprecated request-field fallbacks once clients stop sending them

Open
#1,785 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
344
Forks
47
Avg merge
4d 4h
Merged PRs (30d)
26

Description

Handler fallbacks that honor deprecated request shapes, blocked until the API formally drops those fields:

  • internal/api/v1beta1connect/billing_usage.go — since (superseded by start_range)
  • internal/api/v1beta1connect/billing_subscription.go — flat plan/immediate (superseded by plan_change)
  • internal/api/v1beta1connect/permission.go — namespace/name body fields (superseded by key)
  • internal/api/v1beta1connect/permission_check.go — split object fields (superseded by resource)
  • cmd/serve.go — the FullyConsistent config flag (superseded by consistency)
  • cmd/seed.go — seed data sends the deprecated permission body shape

Part of #1782.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading #1782 to confirm that the API fields have formally been dropped, then inspect the listed handlers and seed/config entry points. Trace each deprecated fallback before removing it and verify that current request shapes and consistency configuration still work. Done means the old fields are no longer honored and seed data uses the current permission body shape.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.