Skip to content

Conversation

@ipmb
Copy link
Member

@ipmb ipmb commented Sep 22, 2025

Summary

  • Ensures apppack.toml is included in build artifacts when using custom APPPACK_TOML environment variable
  • Adds automatic copying of custom config file to default location after build completion
  • Prevents missing configuration in archived build artifacts

Context

This is a follow-up to PR #11 which added support for reading apppack.toml from a custom location via the APPPACK_TOML environment variable. However, the build artifacts were missing the configuration file when it was read from a non-default location.

Changes

  • Added CopyAppPackTomlToDefault() function to copy custom config to default location
  • Integrated the copy operation into the build process with non-fatal error handling
  • Added comprehensive test coverage for the new functionality
  • Refactored to use DefaultAppPackTomlFilename constant for consistency

Test plan

  • Added unit tests for CopyAppPackTomlToDefault() covering all scenarios
  • Test with default apppack.toml location (no-op case)
  • Test with custom APPPACK_TOML path to verify copy works
  • Test with missing custom file to verify graceful error handling
  • Verify build artifacts include apppack.toml after deployment

🤖 Generated with Claude Code

When APPPACK_TOML env var is set to a custom location, the build process
now copies the file to the default location (apppack.toml) after the build
completes. This ensures the configuration is properly included in build
artifacts regardless of its source location.

Changes:
- Add CopyAppPackTomlToDefault() function to handle the copy operation
- Call the function after build completion with non-fatal error handling
- Add comprehensive test coverage for the new functionality
- Use DefaultAppPackTomlFilename constant for consistency

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@ipmb ipmb merged commit e849081 into main Sep 22, 2025
8 checks passed
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.

2 participants