jester/zlh-agent
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

Add database support for tracking customer-selected addons #1

New Issue
Open
opened 2025-12-14 18:19:11 +00:00 by jester · 0 comments
jester commented 2025-12-14 18:19:11 +00:00
Owner
Copy Link

We need to add a DB-backed representation of addons selected per container/customer so the API can:

  • Persist addon selections independent of payload order
  • Expose available vs enabled addons to the frontend
  • Reconstruct the agent payload (state.Config.Addons)

This likely includes:

  • New table (e.g. container_addons or server_addons)
  • API changes to read/write addon selections
  • Clear mapping between DB records and agent payload

This is intentionally deferred until core addon provisioning is stable.

We need to add a DB-backed representation of addons selected per container/customer so the API can: - Persist addon selections independent of payload order - Expose available vs enabled addons to the frontend - Reconstruct the agent payload (state.Config.Addons) This likely includes: - New table (e.g. container_addons or server_addons) - API changes to read/write addon selections - Clear mapping between DB records and agent payload This is intentionally deferred until core addon provisioning is stable.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: jester/zlh-agent#1
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?