feat: runtime endpoint support in AgentCore CLI#979
Merged
Conversation
- Schema: endpoints field on AgentEnvSpec, runtimeVersion in deployed state - Primitive: RuntimeEndpointPrimitive with add/remove/preview - TUI: Add and Remove flows with multi-field form - Status: endpoints nested under agents with deployment badges - Deploy: parseRuntimeEndpointOutputs + buildDeployedState pipeline
The CFN output keys include the AgentEnvironment construct prefix
(Agent{PascalName}) which was missing from the parser pattern.
github-actions
Bot
added
the
agentcore-harness-reviewing
Contributor
Package TarballHow to installnpm install https://github.com/aws/agentcore-cli/releases/download/pr-979-tarball/aws-agentcore-0.11.0.tgz |
![github-code-quality[bot]](https://avatars.githubusercontent.com/u/9919?s=60&v=4){kind=small}
Contributor
Coverage Report
|
github-actions
Bot
removed
the
agentcore-harness-reviewing
- Remove .omc/ from git tracking, add to .gitignore - Remove unused useCallback import in AddRuntimeEndpointScreen.tsx
The description "Named endpoint (version alias) for a runtime" was too long and wrapped to the next line in the Add Resource menu. Shortened to "Named endpoint for a runtime".
- Add explicit Number.isInteger check before schema validation - Change Commander parser from parseInt to Number so floats like 3.5 are caught instead of silently truncated
Endpoint names can collide across runtimes (e.g., both have "prod"). Changed React key from epName to agent.name/epName to prevent duplicate key warnings that pollute the TUI viewport.
When filtering by --type runtime-endpoint, agents array is empty so the agents section (which nests endpoints) never renders. Added a standalone Runtime Endpoints section that shows when endpoints exist but agents don't (i.e., when type-filtering).
The --type option help text was missing runtime-endpoint from the list of valid resource types.
add now returns { success, endpointName, agent, version } instead of
sparse { success: true }, matching the richer response shape from
remove runtime-endpoint.
- TUI: show "Current deployed version: N" and valid range (1-N) - TUI: reject version exceeding latest deployed version - CLI: check deployed-state.json for max version, reject if exceeded - If runtime not deployed, only positive integer check applies
Contributor
Author
Final Verification ReportAll test flows verified with bundle
Full HTML report with inline screenshots: https://gist.github.com/jariy17/f73e36a15be05e18cc92ac09ef6ec67d |
Contributor
Author
|
View the full verification report (rendered HTML with inline screenshots): https://htmlpreview.github.io/?https://gist.githubusercontent.com/jariy17/f73e36a15be05e18cc92ac09ef6ec67d/raw/test-report-final.html |
tejaskash
approved these changes
Apr 27, 2026
Contributor
tejaskash
left a comment
tejaskash
left a comment
There was a problem hiding this comment.
All feedback addressed. Composite keys, parentName field, comprehensive tests, and TUI fixes all look good. One minor nit: dangling JSDoc comment before the closing brace of RuntimeEndpointPrimitive (from the removed findGatewayTargetReferences stub) — can clean up in a follow-up.
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
3 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
endpointsdictionary field toAgentEnvSpecschema for named version aliasesRuntimeEndpointPrimitivewith full add/remove/preview lifecycle[Deployed]/[Local only]badgesparseRuntimeEndpointOutputs+buildDeployedStatetracks endpoint IDs/ARNs indeployed-state.jsonCLI Usage
Known Issue
First-time deploy of runtime + endpoints in same stack creation may fail due to service eventual consistency. Workaround: deploy runtime first, then add endpoints and redeploy.
Depends on
Test plan