feat(agentapi): Add support for running under a subdomain

[johnstcn]

Updates coder/coder#18779

A separate PR will update dependant modules goose and aider.

Description

• Adds subdomain argument to agentapi module
• Updates agentapi module to set AGENTAPI_CHAT_BASE_PATH to an autogenerated path if var.subdomain = false
• Updates default agentapi version to v0.3.3 to support running without subdomain

Type of Change

• New module
• Bug fix
• Feature/enhancement
• Documentation
• Other

Testing & Validation

• Tests pass (bun test)
• Code formatted (bun run fmt)
• Changes tested locally

Related Issues

• bug: /api/v2/users/chat/workspace/embed returns "user" must be an existing uuid or username. coder#18779

[Copilot]

Pull Request Overview

This PR adds support for running the agentapi module under a subdomain by introducing a new agentapi_subdomain variable. When subdomain is disabled, the module configures a custom chat base path to ensure proper routing.

Key changes:

• Added agentapi_subdomain boolean variable with validation to ensure compatibility with agentapi >= v0.3.2
• Updated default agentapi version to v0.3.2 to support the new functionality
• Modified scripts to conditionally set --chat-base-path when subdomain is false

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
main.tf	Adds subdomain variable, validation logic, and chat base path configuration
scripts/main.sh	Exports AGENTAPI_CHAT_BASE_PATH environment variable
testdata/agentapi-start.sh	Updates agentapi server command to include --chat-base-path when needed
test-util.ts	Enhances container cleanup with debug mode support
main.test.ts	Adds comprehensive tests for subdomain functionality and version validation

Comments suppressed due to low confidence (2)

registry/coder/modules/agentapi/main.test.ts:212

• The test case expects setup() to reject with validation errors, but setup() may not be the function that performs Terraform validation. Consider testing the validation logic more directly or ensuring this test actually triggers the validation failure.

        expect(setup({ moduleVariables: moduleVariables as Record<string, string> })).rejects.toThrow(shouldThrow);

registry/coder/modules/agentapi/main.test.ts:214

• The test expects setup() to resolve, but doesn't await the promise. This could lead to unhandled promise rejections or false positive test results. Consider using 'await expect(setup(...)).resolves.toBeDefined()' or properly handling the async expectation.

        expect(setup({ moduleVariables: moduleVariables as Record<string, string> })).resolves.toBeDefined();

[github-actions]

❌ Version Bump Validation Failed

Bump Type: minor

Module versions need to be updated but haven't been bumped yet.

Required Actions:

1. Run the version bump script locally: ./.github/scripts/version-bump.sh minor
2. Commit the changes: git add . && git commit -m "chore: bump module versions (minor)"
3. Push the changes: git push

Script Output:

🔍 Detecting modified modules...
Found modules:
registry/coder/modules/agentapi

📦 Processing: coder/agentapi
Found git tag: release/coder/agentapi/v1.0.2 (v1.0.2)
Current version: 1.0.2
New version: 1.1.0
Updating version references for coder/agentapi in registry/coder/modules/agentapi/README.md

🔧 Running formatter to ensure consistent formatting...

📋 Summary:
Bump Type: minor

Modules Updated:

- coder/agentapi: v1.0.2 → v1.1.0

READMEs Updated:

- coder/agentapi

✅ Version bump completed successfully!
📝 README files have been updated with new versions.

Next steps:
1. Review the changes: git diff
2. Commit the changes: git add . && git commit -m 'chore: bump module versions (minor)'
3. Push the changes: git push

Please update the module versions and push the changes to continue.

[hugodutka]

Other than the comments I left, the PR looks good to me. 👍 Please address them before merging. I'll release agentapi v0.3.3 shortly.