Skip to content

fix: self-guard resource names to prevent multi-stack collisions#1

Open
mayakost wants to merge 1 commit into
mainfrom
feat/context-stack-name
Open

fix: self-guard resource names to prevent multi-stack collisions#1
mayakost wants to merge 1 commit into
mainfrom
feat/context-stack-name

Conversation

@mayakost
Copy link
Copy Markdown
Owner

Summary

Port of aws-samples#70.

Fixes multi-stack name collisions by making each resource self-guard its own name length, rather than imposing a central stackName length limit.

Resource Name derivation Guard
Runtime jean_cloude_${stackName} sanitized .slice(0, 48)
Guardrail task-input-guardrail-${stackName} .slice(0, 50)
Memory bgagent_memory_${stackName} sanitized .slice(0, 48)
Model Invocation Logging Remove onDelete — account-level singleton N/A

Also includes gitleaks allowlist for test fixture signing secret.

Test plan

  • mise //cdk:compile passes
  • mise //cdk:test passes
  • Deploy two stacks in same account without name collisions

Each resource with a name uniqueness constraint now truncates to its
own API limit, removing the need for a central stackName length check:
- Guardrail: ${stackName}-guardrail (.slice(0, 50))
- Memory: bgagent_memory_${stackName} (.slice(0, 48))
- Runtime: sanitize + .slice(0, 48), ensure starts with letter
- Model invocation logging: remove onDelete (account-level singleton)
- Gitleaks: allowlist test fixture signing secret

Based on aws-samples#70
@mayakost
Copy link
Copy Markdown
Owner Author

Background agent — CANCELLED

Field Value
Task 01KREP0XGEN0BN1QPA82JD1P5Q
Repo mayakost/sample-autonomous-cloud-coding-agents
Status CANCELLED
Last event task_cancelled @ 2026-05-12T18:19:53.119Z

@mayakost
Copy link
Copy Markdown
Owner Author

mayakost commented May 13, 2026

Background agent — COMPLETED

Field Value
Task 01KRGYAR749AY9J43NQ1A9NHEW
Repo mayakost/sample-autonomous-cloud-coding-agents
Status COMPLETED
Last event task_completed @ 2026-05-13T15:34:01.437Z
Pull request link
Duration 1269.6s
Cost $1.8676

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant