didericis/bot-bottle
1
0
Fork 0
Code Issues 5 Pull Requests 3 Actions Packages Projects Releases Wiki Activity

feat(bottle): composition via extends: (PRD 0025, issue #88) #89

Merged
didericis merged 5 commits from bottle-extends-prd-0025 into main 2026-05-28 01:26:46 -04:00
Conversation 7 Commits 5 Files Changed 17
+30
1 changed files with 30 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 85104742ca - Show all commits
README.md
+30
View File
@@ -248,6 +248,36 @@ with a warning. **This is the trust boundary**: bottle infrastructure
directory only. A cloned repo cannot redirect a host env var to an directory only. A cloned repo cannot redirect a host env var to an
attacker-named upstream because it has no way to declare a bottle. attacker-named upstream because it has no way to declare a bottle.
### Bottle composition with `extends:`
A bottle can inherit from another via `extends: <bottle-name>` so
operators don't have to duplicate a whole bottle file to vary one
field (PRD 0025). The parent's resolved config is the base; the
child's declared fields overlay. Merge rules:
- `env:` — dict merge, child wins on key collision.
- `git:`, `egress:`, `supervise:` — full replace when the child
didericis commented 2026-05-27 23:37:11 -04:00
Outdated
Review
Copy Link
Copy Source

we should probably refactor how the git config is structured: there should be two subkeys, “user” and “remotes”.

  • “user” has the username and email fields, and is merged with the parent. child wins on duplicate keys
  • “remotes” is a dict keyed by host name. rest of the git config goes as a dict value

Weigh in on the design/wait for feedback before implementing

we should probably refactor how the git config is structured: there should be two subkeys, “user” and “remotes”. - “user” has the username and email fields, and is merged with the parent. child wins on duplicate keys - “remotes” is a dict keyed by host name. rest of the git config goes as a dict value Weigh in on the design/wait for feedback before implementing
declares the field. An explicit `git: []` clears the parent's
list; omitting the field inherits the parent's verbatim.
- `git_user:` — per-field overlay (child's non-empty `name` /
`email` wins; empty falls through to parent).
```yaml
---
extends: dev # inherit everything from bottles/dev.md
egress:
routes:
- host: staging.example.com
auth:
scheme: Bearer
token_ref: STAGING_TOKEN
---
```
Cycles (`A extends B extends A`), self-references, and missing
parents die at parse with a clear pointer. Bottles remain
`$HOME`-only — `extends:` preserves the trust boundary above.
### Example bottle (`~/.claude-bottle/bottles/gitea-dev.md`) ### Example bottle (`~/.claude-bottle/bottles/gitea-dev.md`)
````markdown ````markdown