feat(augment): auto-create chatAgents entry on Kagenti agent deploy#3206
Merged
pkliczewski merged 2 commits intoMay 21, 2026
Merged
Conversation
When a Kagenti agent is successfully created via POST /kagenti/agents, the handler now auto-creates a corresponding chatAgents config entry with lifecycle stage "draft". This bridges the gap between Kagenti infrastructure deployment and the lifecycle governance system, enabling newly created agents to immediately appear in the lifecycle stepper and support submit-for-review flow. Changes: - Add adminConfig and getUserRef to KagentiRouteRegistrarContext - POST /kagenti/agents now auto-creates chatAgents entry with createdBy field on successful deploy - DELETE /kagenti/agents/:ns/:name now cleans up chatAgents entry - Add createdBy field to ChatAgentConfig type (augment-common)
Missing ChangesetsThe following package(s) are changed by this PR but do not have a changeset:
See CONTRIBUTING.md for more information about how to add changesets. Changed Packages
|
9 tasks
|
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #3206 +/- ##
==========================================
- Coverage 53.41% 53.40% -0.02%
==========================================
Files 2373 2373
Lines 84895 84924 +29
Branches 23568 23581 +13
==========================================
+ Hits 45349 45352 +3
+ Misses 39200 38023 -1177
- Partials 346 1549 +1203
*This pull request uses carry forward flags. Click here to find out more. Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
pkliczewski
approved these changes
May 21, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
POST /kagenti/agents, the handler now auto-creates achatAgentsconfig entry withlifecycleStage: "draft"andcreatedByset to the current userDELETE /kagenti/agents/:ns/:name, the handler also cleans up the correspondingchatAgentsconfig entrycreatedByfield toChatAgentConfigtype in augment-commonThis bridges the gap between Kagenti infrastructure deployment and the lifecycle governance system, unblocking the "submit for review" flow for newly deployed agents.
Part of the Agent Lifecycle Governance Epic.
Test plan