Skip to content

Feature Lifecycle tags #7433

@kyle-ssg

Description

@kyle-ssg

Is your feature request related to a problem?

We want to make feature lifecycle GA, the current solution stitched endpoints together in a way that's not viable for production

Image

Describe the solution you'd like.

In order to highlight the lifecycle elsewhere in the platform the best solution seems to be to tag the features based on their lifecycle state. The logic for the lifecycle is as follows:

Backend:

Tag Stale? Code refs? Evals? Meaning
New no 0 Created flag, code not yet wired up
Live no >0 >0 Healthy. In code, not stale
Permanent Already exists
Stale yes >0 Still in code but unchanged long time. Clean up the code
Monitor (Needs Monitoring) yes 0 >0 Code gone but SDKs still ask. Cached deploys, unscanned repos, old clients. Don't delete yet
Remove (To Remove) yes 0 0 Code gone, nobody ask. Safe delete

Frontend:

  • Adjust lifecycle pages to filter features based on tags

(The above highlights we can also have a PR open lifecycle state.)

Describe alternatives you've considered

We could have fields against the flags that represent lifecycle but it feels like tags make way more sense since we can filter and see those in a way that makes the most sense for the solution

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions