feat: use coder boundary subcommand #674
Merged
+51
−21
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.
Summary of Changes
Feature: Add
coder boundarysubcommand support as defaultAdds
coder boundarysubcommand as the default method for running boundary eliminating the need to install boundary separately.Changes:
New variable:
use_boundary_directly(default:false)false: Usescoder boundarysubcommand (default, no installation)true: Installs boundary binary from releasecompile_boundary_from_source = true: Compiles from sourceFixed CAP_NET_ADMIN capability issue
coderbinary tocoder-no-capsto strip capabilities (required for boundary)Removed
boundary-runwrapper - no longer usedFiles Modified:
scripts/start.sh- main implementationmain.tf- addeduse_boundary_directlyvariableBehavior:
coder boundarysubcommand (no installation needed)use_boundary_directly = true: Installs boundary from release versioncompile_boundary_from_source = true: Compiles boundary from sourceType of Change
Module Information
Path:
registry/coder/modules/claude-codeNew version:
v4.7.0Breaking change: [ ] Yes [X] No
Testing & Validation
bun test)bun fmt)Related Issues