Skip to content

feat(api): add logRetention to project entitlements#359

Merged
RajatPawar merged 2 commits into
mainfrom
feat/log-retention-entitlement
Jun 11, 2026
Merged

feat(api): add logRetention to project entitlements#359
RajatPawar merged 2 commits into
mainfrom
feat/log-retention-entitlement

Conversation

@RajatPawar

Copy link
Copy Markdown
Contributor

What

Adds the logRetention entitlement (the number of days logs are retained) to the Project schema's entitlements, alongside brandingRemoval.

This lets generated clients read entitlements.logRetention.value from GetProject when includeEntitlements=true.

Changes

  • api/api.yaml: added logRetention (object with an integer value) under the Project entitlements properties.
  • api/generated/api.json: regenerated via pnpm run gen:json.

Schema

logRetention:
  type: object
  required: [value]
  description: The number of days that logs are retained for this project.
  properties:
    value:
      type: integer
      description: The log retention period for this project, in days.

Related

Companion server PR (populates the field): amp-labs/server#

🤖 Generated with Claude Code

Add the logRetention entitlement (number of days logs are retained) to
the Project schema's entitlements, alongside brandingRemoval, so clients
can read it from GetProject when includeEntitlements is true.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Rename the entitlement key from logRetention to logRetentionDays so the
unit is self-documenting; a bare value of 3 is otherwise ambiguous
between days, hours, and months. Regenerated api/generated/api.json.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@RajatPawar RajatPawar merged commit 7c12909 into main Jun 11, 2026
2 checks passed
@RajatPawar RajatPawar deleted the feat/log-retention-entitlement branch June 11, 2026 19:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants