Fix AI agent modules to use coder_env instead of coder_agent env #159
Conversation
This change addresses issue #128 by updating AI coding modules to use the coder_env resource for setting environment variables instead of recommending users set them on the coder_agent resource. Changes made: - Updated aider module to use coder_env for AI provider API keys - Updated claude-code module to add variables and coder_env resources for API key and prompts - Updated goose module to add variables and coder_env resources for prompts and API key - Updated documentation in README files to show the new approach - Removed export commands from shell scripts since env vars are now set by coder_env This reduces cognitive load for users and provides a cleaner, more consistent approach to environment variable management in AI modules. Co-authored-by: DevelopmentCats <176868952+DevelopmentCats@users.noreply.github.com>
Can you Make sure to update the tests for each module changed to make sure that the change to using coder env resources matches up with what we are testing. Afterwards run bun fmt and then make sure to update the versions using the version bump script |
Fixes #128
This PR updates AI coding modules to use the
coder_envresource for setting environment variables instead of recommending users set them on thecoder_agentresource.Changes Made
Updated Modules:
coder_envresource for AI provider API keys, removedexportcommands from shell scriptscoder_envresources for API key and prompts, updated documentationcoder_envresources for prompts and API key, updated documentationDocumentation Updates:
coder_agentresourceBenefits
✅ Reduced cognitive load: Users no longer need to manually configure environment variables on
coder_agent✅ Cleaner approach: Environment variables are managed within the modules themselves
✅ Consistent pattern: All AI modules now follow the same pattern for environment variable management
✅ Better encapsulation: Module internals are hidden from users
Testing
terraform validate@DevelopmentCats