Description
I'm not finding an easy way to create a project using agentcore toolkit cli and making it portable. I've found a few gaps such as:
aws-targets.json hardcodes account + region — if you clone the repo elsewhere without it, agentcore deploy fails. But the file is environment-specific so it shouldn't be committed with real values.agentcore/cdk/ is auto-generated — if missing, deploy fails ("no CDK project"), but if you run agentcore create to regenerate it, it refuses because the directory isn't empty.
There's no agentcore init that re-scaffolds just the infrastructure around existing code/config.
It would be very useful to have a way to have portable agentcore.json files and a mechanism to recreate the CDK project from scratch. This can also help with updating CDK to newer versions when agentcore cli is updated.
Acceptance Criteria
- An
agentcore.json created to run in an AWS account can be deployed in a new account with just one command: agentcore deploy
Additional Context
No response
Description
I'm not finding an easy way to create a project using agentcore toolkit cli and making it portable. I've found a few gaps such as:
aws-targets.jsonhardcodes account + region — if you clone the repo elsewhere without it,agentcore deployfails. But the file is environment-specific so it shouldn't be committed with real values.agentcore/cdk/is auto-generated — if missing, deploy fails ("no CDK project"), but if you runagentcore createto regenerate it, it refuses because the directory isn't empty.There's no
agentcore initthat re-scaffolds just the infrastructure around existing code/config.It would be very useful to have a way to have portable
agentcore.jsonfiles and a mechanism to recreate the CDK project from scratch. This can also help with updating CDK to newer versions whenagentcorecli is updated.Acceptance Criteria
agentcore.jsoncreated to run in an AWS account can be deployed in a new account with just one command:agentcore deployAdditional Context
No response