Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-05

File format in the repository

One folder per type, SQL in its own file, dataset names as placeholders and no credentials.

code
ingestia/
  ingestia.json                      manifest
  pipelines/erp-vendas.json
  transformacoes/pedidos-validos.json
  transformacoes/pedidos-validos.sql
  consultas/top-clientes.json
  consultas/top-clientes.sql
  modelos/comercial.json
  paineis/diretoria.json
  agentes/analista-financeiro.json
  fluxos/avisa-a-diretoria.json
  notebooks/score-de-credito.json
  clusters/pequeno.json

Rules#

  • No credentials. Any field that looks like a password or token is left out.
  • No physical environment names. prd_katus_silver.pedidos and dev_katus_silver.pedidos become {{silver}}.pedidos — the same file works in both environments, and the difference between branches shows only the real change. Placeholders: {{bronze}}, {{silver}}, {{gold}}. This also applies to names used as keys inside the files.
  • Always the same. The same definition generates exactly the same bytes; publishing without changing anything does not create a commit.
  • The id stays inside the file. Renaming a dashboard changes the file name, but ingestia keeps recognizing the same dashboard.

ingestia only writes inside its own folder; the rest of the repository is yours.

Related links