Skip to content

Implement Entitlements API in AGPL #3278

Closed

Description

@spikecurtis

Problem

The frontend needs the Entitlements API to decide what features to render, even in the APGL case.

Acceptance Criteria

  1. Run coder features list -o json and get a response with all features not-entitled, no warnings, and has_license false.

Activity

  1. kylecarbs commented on Jul 28, 2022

    @kylecarbs
    Member

    Could the endpoint be /entitlements instead? Features seems redundant.

  2. spikecurtis commented on Jul 28, 2022

    @spikecurtis
    CollaboratorAuthor

    could be. RFC has api/v2/features/entitlements and api/v2/features/enablements but we could drop features from both if you think it's clear enough

  3. self-assigned this
    on Aug 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

apiArea: HTTP API

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions