Populate aliasses in Homer 11

[thomasderooij2]

Hi all,
With Homer 7 we just inserted aliasses in the standalone postgres database. Now with the all-in-one solution that does not seem like a viable approach.
I looked at the docs but there does not seem to be a way to populate the aliasses via API. Are there any other ways? Using Flux for k8s deployment so maybe aliasses could be read from a file that can be mounted somewhere?

Thank you and kind regards, Thomas

[adubovikov]

Hi Thomas — good question. You do not need to insert into Postgres anymore.

Where aliases live

In Homer 11, IP aliases are stored in the Coordinator settings DuckDB (alias table at settings_db_path), not in DuckLake and not in a standalone Postgres. They enrich search/flow rows (aliasSrc / aliasDst).

Populate via API (already supported)

Full CRUD exists on /api/v4/aliases (and the /api/v4/ipaliases mirror). Create / update / delete require an admin session. List and lookup need a normal authenticated token.

Example:

# 1) get a token (admin user)
TOKEN=$(curl -s -X POST "https://homer.example/api/v4/auth/sessions" \
  -H "Content-Type: application/json" \
  -d '{"username":"admin","password":"..."}' | jq -r '.data.token // .token')

# 2) create an alias
curl -s -X POST "https://homer.example/api/v4/aliases" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"alias":"SBC-A","ip":"10.0.0.1","port":0,"mask":32,"status":true}'

You can also manage them in the UI: Settings → IP Aliases.

Diagnostic LPM check: GET /api/v4/aliases/lookup?ip=10.0.0.1&port=0.

Flux / k8s

There is no startup file/env seed for aliases yet (a mounted ConfigMap is not read automatically). For GitOps today, keep the alias list in a ConfigMap/Secret and apply it with a Job (or similar) that authenticates and POSTs to /api/v4/aliases. Direct SQL into the settings DuckDB works technically but the API is the supported path.

If you are migrating from Homer 7, homer-core migrate settings can import the old Postgres alias rows.

I opened a docs PR that makes this explicit in COORDINATOR.md (the Settings section previously only listed GET): #898

OpenAPI (full schemas): src/coordinator/docs/openapi.yaml tag Aliases.

Happy to discuss a future file-seed / bulk-import option if that would help your Flux setup.

[thomasderooij2]

Thanks for the quick reply.

Great to hear it's available via API already. I will just build a small cron script that scrapes our IPAM and inserts the new aliasses every day.