refactor(config): deduplicate exec helpers between secret-store, writer and config-resolver
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 20/100
- Tipo de issue
- Refactorización
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
- Área
- cli
Línea de trabajo
Start by diffing src/config/secret-store.ts, src/config/writer.ts and packages/config-resolver/src/index.ts to confirm the duplicated helpers (shellEscape, psEncodedCommand, PRINTABLE_ASCII_RE, execOpts, the _testSetExecSync/_testSetPlatform seams). The issue says not to start until #664 and the icacls-to-execFile change for writer.ts have landed, so re-check those first. Done means no helper body is defined in more than one file, existing tests pass with only import paths changed, and the lazy load in loader.ts is preserved.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
Process-exec helpers are copy-pasted across three files. Diffed and confirmed byte-identical:
shellEscapeandpsEncodedCommand:src/config/secret-store.ts:88-95andpackages/config-resolver/src/index.ts:139-146.PRINTABLE_ASCII_RE:secret-store.ts:57andconfig-resolver/src/index.ts:184.execOpts:config-resolver/src/index.ts:135-137andsrc/config/writer.ts:59-61are identical.secret-store.ts:77-86is the same with an optionalinput._execSync/_platformplus the_testSetExecSync/_testSetPlatformseams:secret-store.ts:125-148,config-resolver/src/index.ts:132-133,341-351,writer.ts:42-57.
secret-store.ts also defines spawnOpts (L110-119). Its body is identical to execOpts (L77-86); only the return type differs. The security -w … doc comment at L101-106 describes the spawnSync(SETSID_PERL, …) call in MacKeychainStore.put (~L184-195), but it is attached to the SETSID_PERL constant.
Sequencing (do NOT start yet)
- After #664's fix. This comment proposes moving
secret-store.tstoexecFile/spawnargv. That deletes every POSIXshellEscapeuse in that file (L214, 239, 252, 283, 294) and probablyexecOpts/spawnOptsas they are today. - After the icacls →
execFilePR forwriter.ts.writer.tsonly uses_execSyncforicacls(L238). Once that change lands, itsexecOptscopy and_testSetExecSyncseam either go away or change shape.
What remains after both
These are estimates and depend on how #664 lands:
psEncodedCommand(4 lines) is still in bothsecret-store.ts(Windows Credential Manager: L313, 330, 342) andconfig-resolver(L297).PRINTABLE_ASCII_RE(1 line) is in both.shellEscapestays only inconfig-resolver(L215, 238, 264) unless the resolver also moves to argv. It would then no longer be duplicated.- The
_testSetExecSync/_testSetPlatformseams (~10 lines) remain in each file that still shells out.
That leaves roughly 15-25 duplicated lines in total. This is low priority. Once the prerequisites land, re-run the diff first. If only psEncodedCommand and the regex are left, it may be cheaper to leave them and close this issue.
Proposal
- Export
psEncodedCommand(andPRINTABLE_ASCII_RE, plus the exec options builder if one survives) from@elastic/config-resolver, which is already a workspace dependency, and import them insecret-store.ts. Don't add asrc/lib/proc.ts: the package can't import fromsrc/, so the package has to be the source. - Keep it a cheap import.
loader.ts:31,381lazy-loads@elastic/config-resolverto keep the help path fast.secret-store.tsis only reached fromconfigcommands andcloud/credentials.ts, so a static import there should be fine. Check this against ARCHITECTURE.md before merging. - Collapse
execOpts/spawnOptsinto one builder if both still exist. - Move the
security -wcomment onto thespawnSynccall it describes.
Acceptance criteria
- No helper function body is defined in more than one of
src/config/secret-store.ts,src/config/writer.ts,packages/config-resolver/src/index.ts. - At most one exec options builder in
secret-store.ts. - The
security -wcomment sits next to thespawnSynccall inMacKeychainStore.put. - No behavior change. Existing secret-store, writer and config-resolver tests pass unmodified, apart from import paths.
- No regression in help-path startup time (the lazy-load in
loader.tsis preserved).
Related
#664, plus the pending icacls → execFile PR for src/config/writer.ts.
authored by Pi Coding Agent (Claude Opus 5.5)
- Lenguaje dominante
- TypeScript
- Estrellas
- 49
- Forks
- 27
- Merge medio
- 1 d 23 h
- PR fusionados (30 d)
- 67
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de elastic/cli
-
feat: ship skills/elastic/SKILL.md for agent invocationPosiblemente ocupada @onatozmenn la tomó hace 19 días. Abiertoenhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
elastic/cli#628 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
elastic/cli#617 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 38/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 58/100
Los mantenedores suelen responder en 1 día
-
refactor(config): drop unused safeParse wrappers and stale Zod comments in config/schema.tsPosiblemente ocupada @JoshMock la tomó hoy. Abierto
Dificultad 3/5 Medio día Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día
Todos los issues de elastic/cli
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
agilepathway/label-checker#739 · 4 comentarios ·
Los mantenedores suelen responder en 1 día
-
Wrong key location at startupAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 68/100
CopilotKit/OpenBot#800 ·
Los mantenedores suelen responder en 1 día
-
Endpoint links in the tag operations list are below the 24px target sizePosiblemente ocupada @AdzerKI la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
ehmpathy/rhachet-roles-bhuild#471 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
Los mantenedores suelen responder en 1 día