@noeva/etl-core 1.0.0-next.5 → 1.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (85) hide show
  1. package/CHANGELOG.md +183 -0
  2. package/LICENSE +19 -0
  3. package/README.md +1 -1
  4. package/deploy/Dockerfile +1 -1
  5. package/dist/guida/404.html +3 -3
  6. package/dist/guida/GUIDA_SVILUPPO.html +6 -6
  7. package/dist/guida/TECHNICAL_OVERVIEW.html +8 -8
  8. package/dist/guida/assets/{TECHNICAL_OVERVIEW.md.iD1gDlJY.js → TECHNICAL_OVERVIEW.md.DTIhkkg9.js} +1 -1
  9. package/dist/guida/assets/{app.BrI3mcoI.js → app.DlsuGVZn.js} +1 -1
  10. package/dist/guida/assets/chunks/@localSearchIndexroot.LnC621Vy.js +1 -0
  11. package/dist/guida/assets/chunks/{VPLocalSearchBox.BlKLVNlB.js → VPLocalSearchBox.v4vBLemj.js} +2 -2
  12. package/dist/guida/assets/chunks/{theme.Cuah39Zj.js → theme.D9XEK7o0.js} +2 -2
  13. package/dist/guida/assets/{guide_claude-code_index.md.CxVSru8e.js → guide_claude-code_index.md.DEnzf9b_.js} +1 -1
  14. package/dist/guida/assets/{runbooks_aggiornamento-pm2.md.f3LAxif4.js → runbooks_aggiornamento-pm2.md.DrFr4blI.js} +1 -1
  15. package/dist/guida/assets/{runbooks_deployment.md.CsIYRa_5.js → runbooks_deployment.md.CwG77qGO.js} +1 -1
  16. package/dist/guida/assets/{style.BNn_AkzN.css → style.DFlUbYCk.css} +1 -1
  17. package/dist/guida/connectors/README.html +5 -5
  18. package/dist/guida/connectors/file.html +6 -6
  19. package/dist/guida/connectors/http.html +6 -6
  20. package/dist/guida/connectors/imap.html +6 -6
  21. package/dist/guida/connectors/jira.html +6 -6
  22. package/dist/guida/connectors/noeva.html +6 -6
  23. package/dist/guida/connectors/oauth.html +6 -6
  24. package/dist/guida/connectors/postgres.html +6 -6
  25. package/dist/guida/connectors/process.html +6 -6
  26. package/dist/guida/connectors/sendgrid.html +6 -6
  27. package/dist/guida/connectors/smtp.html +6 -6
  28. package/dist/guida/connectors/sqlserver.html +6 -6
  29. package/dist/guida/connectors/zoho.html +6 -6
  30. package/dist/guida/conventions/node-columns.html +6 -6
  31. package/dist/guida/conventions/node-descriptor.html +6 -6
  32. package/dist/guida/conventions/run-report.html +6 -6
  33. package/dist/guida/conventions/run-trace.html +6 -6
  34. package/dist/guida/conventions/variabili-del-core.html +5 -5
  35. package/dist/guida/conventions/versioni-di-pipeline.html +6 -6
  36. package/dist/guida/guide/claude-code/index.html +7 -7
  37. package/dist/guida/guide/claude-code/prompt.html +6 -6
  38. package/dist/guida/guide/claude-code/strumenti.html +5 -5
  39. package/dist/guida/guide/grafo.html +6 -6
  40. package/dist/guida/guide/usare/app-desktop.html +5 -5
  41. package/dist/guida/guide/usare/esito-di-una-run.html +6 -6
  42. package/dist/guida/guide/usare/index.html +5 -5
  43. package/dist/guida/hashmap.json +1 -1
  44. package/dist/guida/index.html +6 -6
  45. package/dist/guida/nodes/README.html +6 -6
  46. package/dist/guida/nodes/action.html +6 -6
  47. package/dist/guida/nodes/ai.html +6 -6
  48. package/dist/guida/nodes/join.html +6 -6
  49. package/dist/guida/nodes/lookup.html +6 -6
  50. package/dist/guida/nodes/pipeline.html +6 -6
  51. package/dist/guida/nodes/route.html +6 -6
  52. package/dist/guida/nodes/sink.html +6 -6
  53. package/dist/guida/nodes/source.html +6 -6
  54. package/dist/guida/nodes/task.html +6 -6
  55. package/dist/guida/nodes/transform.html +6 -6
  56. package/dist/guida/nodes/try-catch.html +6 -6
  57. package/dist/guida/nodes/union.html +6 -6
  58. package/dist/guida/pipelines/README.html +6 -6
  59. package/dist/guida/pipelines/crm-leads-sync.html +6 -6
  60. package/dist/guida/pipelines/cross-workspace-csv-merge.html +6 -6
  61. package/dist/guida/pipelines/movimenti-per-conto.html +6 -6
  62. package/dist/guida/pipelines/orders-enriched-daily.html +6 -6
  63. package/dist/guida/pipelines/test-posta.html +6 -6
  64. package/dist/guida/runbooks/aggiornamento-pm2.html +7 -7
  65. package/dist/guida/runbooks/deploy-ecr.html +6 -6
  66. package/dist/guida/runbooks/deployment.html +8 -8
  67. package/dist/guida/runbooks/etl-worker.html +6 -6
  68. package/dist/guida/runbooks/graph-server.html +6 -6
  69. package/dist/guida/runbooks/mask-key.html +6 -6
  70. package/dist/guida/runbooks/oauth-google-posta.html +6 -6
  71. package/dist/guida/runbooks/rollback-di-pipeline.html +6 -6
  72. package/dist/guida/runbooks/scd2-rehash.html +6 -6
  73. package/dist/guida/runbooks/sql-task-truncate-swap.html +6 -6
  74. package/dist/guida/runbooks/stato-incrementale.html +6 -6
  75. package/dist/guida/sub-pipelines/README.html +6 -6
  76. package/dist/guida/sub-pipelines/riepilogo-ordini.html +6 -6
  77. package/kit/boilerplate/.github/workflows/ci.yml +1 -1
  78. package/kit/boilerplate/.github/workflows/image.yml +1 -1
  79. package/kit/boilerplate/package.json +1 -1
  80. package/package.json +5 -4
  81. package/dist/guida/assets/chunks/@localSearchIndexroot.DjrQYH6x.js +0 -1
  82. /package/dist/guida/assets/{TECHNICAL_OVERVIEW.md.iD1gDlJY.lean.js → TECHNICAL_OVERVIEW.md.DTIhkkg9.lean.js} +0 -0
  83. /package/dist/guida/assets/{guide_claude-code_index.md.CxVSru8e.lean.js → guide_claude-code_index.md.DEnzf9b_.lean.js} +0 -0
  84. /package/dist/guida/assets/{runbooks_aggiornamento-pm2.md.f3LAxif4.lean.js → runbooks_aggiornamento-pm2.md.DrFr4blI.lean.js} +0 -0
  85. /package/dist/guida/assets/{runbooks_deployment.md.CsIYRa_5.lean.js → runbooks_deployment.md.CwG77qGO.lean.js} +0 -0
@@ -2,7 +2,7 @@ import{_ as e,o as s,c as a,a5 as n}from"./chunks/framework.qdetmeNX.js";const c
2
2
  <span class="line"><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">etl</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> run</span><span style="--shiki-light:#D73A49;--shiki-dark:#F97583;"> &lt;</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;">pipelin</span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;">e</span><span style="--shiki-light:#D73A49;--shiki-dark:#F97583;">&gt;</span><span style="--shiki-light:#6A737D;--shiki-dark:#6A737D;"> # esegue una pipeline</span></span>
3
3
  <span class="line"><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">etl</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> serve</span><span style="--shiki-light:#6A737D;--shiki-dark:#6A737D;"> # default dell&#39;immagine: grafi via HTTP + worker</span></span>
4
4
  <span class="line"><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">etl</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> worker</span><span style="--shiki-light:#6A737D;--shiki-dark:#6A737D;"> # solo i worker</span></span>
5
- <span class="line"><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">etl</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> deploy-ecr</span><span style="--shiki-light:#D73A49;--shiki-dark:#F97583;"> &lt;</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;">client</span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;">e</span><span style="--shiki-light:#D73A49;--shiki-dark:#F97583;">&gt;</span><span style="--shiki-light:#6A737D;--shiki-dark:#6A737D;"> # l&#39;immagine di un cliente su ECR + ECS (sotto)</span></span></code></pre></div><p>Prima di ogni comando la CLI carica da sola il <code>.env</code> alla radice del repo, se c&#39;è, e le variabili già nel processo vincono: <code>etl run</code> da un terminale vede lo stesso ambiente di <code>etl serve</code> sotto PM2. Nell&#39;immagine il <code>.env</code> non c&#39;è (lo esclude il contesto della build), e l&#39;ambiente arriva da <code>docker run --env-file</code> o dall&#39;orchestratore.</p><h2 id="immagine-del-repo-cliente" tabindex="-1">Immagine del repo cliente <a class="header-anchor" href="#immagine-del-repo-cliente" aria-label="Permalink to &quot;Immagine del repo cliente&quot;">​</a></h2><p>Il Dockerfile non sta nel repo cliente: lo porta il pacchetto del core, <code>@noeva/etl-core/deploy/Dockerfile</code>, con il suo <code>Dockerfile.dockerignore</code> accanto, e arriva aggiornato con il bump. L&#39;immagine parte da <code>node:20-slim</code> e installa il repo con <code>pnpm install --prod --frozen-lockfile</code>: il core arriva dal lockfile come ogni altra dipendenza, e non c&#39;è un&#39;immagine base del core. Non c&#39;è build del codice, che gira dai sorgenti con <code>tsx</code>; si costruisce invece la documentazione del cliente (<code>etl docs build</code>), che <code>etl serve</code> mostra su <code>/guida/</code>, mentre la guida del core su <code>/guida/core/</code> è già costruita nel pacchetto installato. <code>ENTRYPOINT</code> è <code>etl</code> e <code>CMD</code> è <code>serve</code>, quindi <code>… run &lt;pipeline&gt;</code> lancia una run sola.</p><p><strong>La costruisce <code>image.yml</code></strong>, il file gestito che <code>etl init</code> scrive nel repo cliente, lanciato a mano (Actions → Immagine → Run workflow) o spingendo un tag <code>v*</code>, mai a ogni push:</p><ul><li>pubblica su <code>ghcr.io/&lt;owner&gt;/noeva-etl-&lt;slug&gt;</code>, il GHCR dell&#39;owner del repo, con <code>GITHUB_TOKEN</code>, che dopo un transfer segue il repo;</li><li><strong>il tag è lo SHA del commit</strong>, sempre, più un tag facoltativo: quello dato a mano o il tag git spinto. Niente <code>latest</code> né timestamp: il workflow rifiuta <code>latest</code>. Il deploy cita lo SHA, e il rollback del deploy è «torna allo SHA precedente»;</li><li>il core si installa da npmjs <strong>senza credenziali</strong> (ADR-0105): nessun segreto entra nella build;</li><li><code>ETL_RELEASE</code> arriva come build arg, <code>git:&lt;sha a 12 caratteri&gt;</code>, ed è la release che il report di ogni run registra, accanto a <code>core</code> e <code>client</code>.</li></ul><p><strong>In locale</strong>, dalla radice del repo cliente e dopo <code>pnpm install</code> (il Dockerfile sta in <code>node_modules</code>):</p><div class="language-bash vp-adaptive-theme"><button title="Copy Code" class="copy"></button><span class="lang">bash</span><pre class="shiki shiki-themes github-light github-dark vp-code" tabindex="0"><code><span class="line"><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">docker</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> build</span><span style="--shiki-light:#005CC5;--shiki-dark:#79B8FF;"> \\</span></span>
5
+ <span class="line"><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">etl</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> deploy-ecr</span><span style="--shiki-light:#D73A49;--shiki-dark:#F97583;"> &lt;</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;">client</span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;">e</span><span style="--shiki-light:#D73A49;--shiki-dark:#F97583;">&gt;</span><span style="--shiki-light:#6A737D;--shiki-dark:#6A737D;"> # l&#39;immagine di un cliente su ECR + ECS (sotto)</span></span></code></pre></div><p>Prima di ogni comando la CLI carica da sola il <code>.env</code> alla radice del repo, se c&#39;è, e le variabili già nel processo vincono: <code>etl run</code> da un terminale vede lo stesso ambiente di <code>etl serve</code> sotto PM2. Nell&#39;immagine il <code>.env</code> non c&#39;è (lo esclude il contesto della build), e l&#39;ambiente arriva da <code>docker run --env-file</code> o dall&#39;orchestratore.</p><h2 id="immagine-del-repo-cliente" tabindex="-1">Immagine del repo cliente <a class="header-anchor" href="#immagine-del-repo-cliente" aria-label="Permalink to &quot;Immagine del repo cliente&quot;">​</a></h2><p>Il Dockerfile non sta nel repo cliente: lo porta il pacchetto del core, <code>@noeva/etl-core/deploy/Dockerfile</code>, con il suo <code>Dockerfile.dockerignore</code> accanto, e arriva aggiornato con il bump. L&#39;immagine parte da <code>node:26-slim</code> e installa il repo con <code>pnpm install --prod --frozen-lockfile</code>: il core arriva dal lockfile come ogni altra dipendenza, e non c&#39;è un&#39;immagine base del core. Non c&#39;è build del codice, che gira dai sorgenti con <code>tsx</code>; si costruisce invece la documentazione del cliente (<code>etl docs build</code>), che <code>etl serve</code> mostra su <code>/guida/</code>, mentre la guida del core su <code>/guida/core/</code> è già costruita nel pacchetto installato. <code>ENTRYPOINT</code> è <code>etl</code> e <code>CMD</code> è <code>serve</code>, quindi <code>… run &lt;pipeline&gt;</code> lancia una run sola.</p><p><strong>La costruisce <code>image.yml</code></strong>, il file gestito che <code>etl init</code> scrive nel repo cliente, lanciato a mano (Actions → Immagine → Run workflow) o spingendo un tag <code>v*</code>, mai a ogni push:</p><ul><li>pubblica su <code>ghcr.io/&lt;owner&gt;/noeva-etl-&lt;slug&gt;</code>, il GHCR dell&#39;owner del repo, con <code>GITHUB_TOKEN</code>, che dopo un transfer segue il repo;</li><li><strong>il tag è lo SHA del commit</strong>, sempre, più un tag facoltativo: quello dato a mano o il tag git spinto. Niente <code>latest</code> né timestamp: il workflow rifiuta <code>latest</code>. Il deploy cita lo SHA, e il rollback del deploy è «torna allo SHA precedente»;</li><li>il core si installa da npmjs <strong>senza credenziali</strong> (ADR-0105): nessun segreto entra nella build;</li><li><code>ETL_RELEASE</code> arriva come build arg, <code>git:&lt;sha a 12 caratteri&gt;</code>, ed è la release che il report di ogni run registra, accanto a <code>core</code> e <code>client</code>.</li></ul><p><strong>In locale</strong>, dalla radice del repo cliente e dopo <code>pnpm install</code> (il Dockerfile sta in <code>node_modules</code>):</p><div class="language-bash vp-adaptive-theme"><button title="Copy Code" class="copy"></button><span class="lang">bash</span><pre class="shiki shiki-themes github-light github-dark vp-code" tabindex="0"><code><span class="line"><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">docker</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> build</span><span style="--shiki-light:#005CC5;--shiki-dark:#79B8FF;"> \\</span></span>
6
6
  <span class="line"><span style="--shiki-light:#005CC5;--shiki-dark:#79B8FF;"> -f</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> node_modules/@noeva/etl-core/deploy/Dockerfile</span><span style="--shiki-light:#005CC5;--shiki-dark:#79B8FF;"> \\</span></span>
7
7
  <span class="line"><span style="--shiki-light:#005CC5;--shiki-dark:#79B8FF;"> --build-arg</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> ETL_RELEASE=git:</span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;">$(</span><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">git</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> rev-parse</span><span style="--shiki-light:#005CC5;--shiki-dark:#79B8FF;"> --short=12</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> HEAD</span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;">) </span><span style="--shiki-light:#005CC5;--shiki-dark:#79B8FF;">\\</span></span>
8
8
  <span class="line"><span style="--shiki-light:#005CC5;--shiki-dark:#79B8FF;"> -t</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> noeva-etl-</span><span style="--shiki-light:#D73A49;--shiki-dark:#F97583;">&lt;</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;">slu</span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;">g</span><span style="--shiki-light:#D73A49;--shiki-dark:#F97583;">&gt;</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;">:</span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;">$(</span><span style="--shiki-light:#6F42C1;--shiki-dark:#B392F0;">git</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> rev-parse</span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;"> HEAD</span><span style="--shiki-light:#24292E;--shiki-dark:#E1E4E8;">) </span><span style="--shiki-light:#032F62;--shiki-dark:#9ECBFF;">.</span></span>