Skip to content

fix(manager): use HICLAW_PROXY_CONTAINER_PREFIX for cms tracing naming consistency#530

Draft
Jing-ze wants to merge 1 commit intoagentscope-ai:mainfrom
Jing-ze:worktree-fix-cms-worker-prefix
Draft

fix(manager): use HICLAW_PROXY_CONTAINER_PREFIX for cms tracing naming consistency#530
Jing-ze wants to merge 1 commit intoagentscope-ai:mainfrom
Jing-ze:worktree-fix-cms-worker-prefix

Conversation

@Jing-ze
Copy link
Copy Markdown
Contributor

@Jing-ze Jing-ze commented Apr 2, 2026

Summary

  • docker-proxy already reads HICLAW_PROXY_CONTAINER_PREFIX to validate container names, but container-api.sh and generate-worker-config.sh had the prefix hardcoded to hiclaw-worker-. This caused mismatches when a custom prefix was configured — container operations and CMS service names wouldn't align with the proxy's security rules.
  • Now all three components read the same env var with the same default.

Test plan

  • Deploy with default config (no HICLAW_PROXY_CONTAINER_PREFIX set) — verify worker containers and CMS traces still use hiclaw-worker-<name>
  • Set HICLAW_PROXY_CONTAINER_PREFIX=custom- and verify container names and CMS service names both use custom-<name>

🤖 Generated with Claude Code

…sistency

Align container-api.sh and CMS service name with the same
HICLAW_PROXY_CONTAINER_PREFIX env var already used by docker-proxy,
so custom prefixes propagate to container management and observability.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@Jing-ze Jing-ze changed the title fix(manager): use HICLAW_PROXY_CONTAINER_PREFIX for worker naming consistency fix(manager): use HICLAW_PROXY_CONTAINER_PREFIX for cms tracing naming consistency Apr 2, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 2, 2026

❌ Integration Tests Failed

Commit: e8cb876
Workflow run: #561

Test Results
No test output captured.
Debug Log (tail)
No debug logs available.

📦 Download full debug logs & test artifacts

@Jing-ze Jing-ze marked this pull request as draft April 2, 2026 06:05
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