feat: support individual memory deployment without agents#483
Open
feat: support individual memory deployment without agents#483
Conversation
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
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.
Description
Enables memory-only deployments — users can deploy memory resources without defining any agents. Adds per-memory output parsing from CloudFormation into
deployed-state.json, removes the agent-gating on the memory add flow, and updates preflight validation.Known limitation:
agentcore statusdoes not yet work for memory-only projects. That will be a fast-follow or could be taken up with issue #473Related Issue
Closes #482
Documentation PR
N/A
Type of Change
Testing
npm run test:unitandnpm run test:integnpm run typechecknpm run lintdeployed-state.jsoncontainsmemoryIdandmemoryArnChecklist
Depends on CDK companion PR: aws/agentcore-l3-cdk-constructs#62
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.