Skip to content

(feat) SDK: allow setting display names for apps and variants #4663

@mmabrouk

Description

@mmabrouk

When you create an app through the Python SDK, you cannot give it (or its variant) a human-readable display name. Everything ends up labeled by its slug or not labeled at all, and the UI surfaces show slugs or dashes instead of proper names.

Current behavior

  • AppManager.create (sdks/python/agenta/sdk/managers/apps.py) accepts only app_slug. The payload builder _build_simple_application_payload (lines 26-29) hardcodes "name": app_slug, so apps created via the SDK are always named after their slug (e.g. "cv-screening" instead of "CV Screening").
  • VariantManager.create / VariantManager.commit (sdks/python/agenta/sdk/managers/variant.py) accept only slugs. There is no name parameter at all, so SDK-created variants get name: NULL and committed revisions get name: NULL.

Real-world impact (from the cv-screening example app on the dev deployment), the variants query returns:

slug: default | name: None

and revisions return name: None. The UI then shows "--" or hex slugs as labels (tracked in #4662 / GitHub #4662).

A temporary backend fix is being prepared in parallel that defaults variant.name to its slug at creation. This issue tracks the proper SDK fix that makes that default unnecessary for new SDKs.

Desired behavior

  • AppManager.create accepts an optional app_name= parameter that sets the app's display name (instead of hardcoding name=slug).
  • VariantManager.create and VariantManager.commit accept optional display-name parameters that flow to the created variant, so variants and their revisions carry a human-readable name.

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions