feat: split public capabilities from entitlement details - #28479
Closed
jaaydenh wants to merge 2 commits into
Closed
feat: split public capabilities from entitlement details#28479jaaydenh wants to merge 2 commits into
jaaydenh wants to merge 2 commits into
Conversation
Contributor
Docs previewCheck off each page once it's been reviewed. If a page changes in a later push, its checkbox clears automatically so it gets a fresh look. Pages not yet wired into the docs navigation aren't listed here. |
Contributor
Author
|
Superseded by the two-PR stack:
The replacement branches are based on the current main branch and preserve the combined implementation as a reviewable stack. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a public deployment-capabilities contract while keeping limits, usage, warnings, and errors in the authenticated entitlements response. The dashboard and HTML shell now use the sanitized capability projection, while detail-only UI fetches full entitlements separately.
Problem
GET /api/v2/entitlementswas anonymously accessible and its complete response was embedded in authenticated HTML, exposing commercial limits and deployment usage details. Community deployments also recorded Coder Agent runtime but did not surface that usage in settings.Fix
Add
GET /api/v2/deployment/capabilities, compute feature usability on the backend, require authentication for full entitlements, and split the frontend capability and detail caches. Aggregate retained Community Agent Time without changing the five-agent concurrency cap, and show Community, finite-license, unlimited-license, loading, and unavailable states in Coder Agents settings. Existing authenticated SDK, CLI, and support-bundle callers continue using the full entitlements contract.Refs CODAGT-960
Refs CODAGT-890