lei.chen/myxce
1
0
Fork 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(controller-peers-env-fallback): pin the generated xceadmin wrapper to its own deployment (task 5.1)

Browse source 
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Rongsong Shen 2026-10-03 08:04:03 +00:00
parent 148507980b
commit ac7a43855d
Signed by untrusted user: rshen
GPG key ID: 80533536B0EB651C
3 changed files with 72 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.kiro/specs/controller-peers-env-fallback/tasks.md
View file

@ -96,7 +96,7 @@
- _Depends: 4.1, 4.2_
- [ ] 5. Integration
- [ ] 5.1 Pin the generated xceadmin wrapper to its own deployment
- [x] 5.1 Pin the generated xceadmin wrapper to its own deployment
- Add the wrapper case to the regression script first and see it fail: generate a deployment on free high ports into a scratch directory, run a copy of the generated wrapper whose final line prints the two variables, with a bogus value of the new variable in the caller's environment, and expect the deployment's own `ctrl-N=host:port` list and first candidate; fail with a message naming the xceadmin build when the wheel is missing
- In the deploy script's generated wrapper, export the new variable set to the deployment's full peers list next to the existing legacy export, and extend the comment above it to say why
- Done when, with the xceadmin wheel built (`/xce-build xceadmin`), the wrapper case in the regression script passes