feat: allow profile-specific runner builds - #477
Open
Hyperkid123 wants to merge 1 commit into
Open
Hyperkid123 wants to merge 1 commit into
Hyperkid123 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Add opt-in
INSTANCE_CONFIG_PATHbuild argument for multi-profile runner repositories. Selected builds install and initialize only requested profile env presets; omitted argument preserves existing union behavior.No Jira ticket supplied.
Blast radius
Runner images using
Dockerfile.runner; existing consumers unchanged unless they pass new build argument.Rollback plan
Git revert is sufficient. Removing
INSTANCE_CONFIG_PATHrestores existing union behavior.Checklist
bash -n presets/install-envs.sh entrypoint.shpytest -q bot/tests/test_instance_config.py(23 passed)AI disclosure
Assisted by: Claude Code