Skip to content

Differentiate between releases which should live indefinitely, vs. those which are intended to be temporary #86

@tcatling

Description

@tcatling

The helm process will always be fallible because it is only client side, and eventually we will want some kind of platform-level garbage collection. --no-sandbox-cleanup and sandbox services for human baselining mean that some sandbox releases are intended to live indefinitely, whereas we expect most to be 'temporary'. It would be great if we could have some kind of TTL label on releases (components of releases) which could make it clearer if they are obviously expired.

This could look like putting a TTL label of $INSPECT_SANDBOX_TTL on releases which are not expected to live forever. By default this value could be large enough to accommodate all current evals, e.g. 24hrs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions