Repository navigation
refactor(e2e): call framework.DevsySSH directly - #1486
Conversation
Drop the duplicated execSSH forwarder on baseTestContext in the up and up-docker-compose e2e packages. Call sites now use btc.f.DevsySSH directly with unchanged arguments. execSSHCapture is untouched.
✅ Deploy Preview for images-devsy-sh canceled.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
✅ Deploy Preview for devsydev canceled.
|
|
This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again. |
What changed
execSSHforwarder method onbaseTestContextine2e/tests/up/helper.goande2e/tests/up-docker-compose/helper.go. It only forwarded tobtc.f.DevsySSH(ctx, tempDir, command).<recv>.execSSH(...)call sites to<recv>.f.DevsySSH(...)with the same arguments in the same order. Files:up/{helper,provider_docker,sops,up_behaviors}.go,up-docker-compose/{config,up_docker_compose}.go.execSSHCapture(runsdevsy workspace ssh --command) is unchanged, along with its callers.execSSHidentifier.task cli:formatthen re-wrapped about 20 calls that became too long. Those are formatter-only line wraps.Why
Same duplicated-forwarder theme as #1481.
execSSHadded no behaviour overframework.DevsySSH, so the indirection is removed and callers use the framework method directly.Verification
git grep -n "\.execSSH(" -- e2e: no matches.task cli:format: exit 0, only the 7 touched files changed.task cli:lint:ci: exit 0, 0 issues.go vet ./e2e/...: exit 0.go test -count=1 -run xxx ./e2e/...: exit 0 (compile-only).upandup-docker-composecompile.CodeRabbit CLI
coderabbit review --agent --committed --base-commit 21c01dd5completed with 0 findings across the 7 reviewed files.Skipped findings
None.
Summary by CodeRabbit