updates to allow for testing services with notifications

[tonytheleg]

PR Template:

Describe your changes

• Adds an alternate SpiceDB compose setup that uses a different postgres since everything wants to use the default port
• Adds related make target for spinning that up
• Adds doc on running notifications + inventory + relations locally using binaries and compose

Ticket reference (if applicable)

Fixes #

Checklist

• Are the agreed upon acceptance criteria fulfilled?

• Was the 4-eye-principle applied? (async PR review, pairing, ensembling)

• Do your changes have passing automated tests and sufficient observability?

• Are the work steps you introduced repeatable by others, either through automation or documentation?

  • If automation is possible but not done due to other constraints, a ticket to the tech debt sprint is added
  • An SOP (Standard Operating Procedure) was created

• The Changes were automatically built, tested, and - if needed, behind a feature flag - deployed to our production environment. (Please check this when the new deployment is done and you could verify it.)

• Are the agreed upon coding/architectural practices applied?

• Are security needs fullfilled? (e.g. no internal URL)

• Is the corresponding Ticket in the right state? (should be on "review" now, put to done when this change made it to production)

• For changes to the public API / code dependencies: Was the whole team (or a sufficient amount of ppl) able to review?

[merlante]

Do the steps in this link bring up a db to work with gorm? make migrate makes me think of an in-memory db maybe?

[tonytheleg]

Yes, the config is setup to use sqllite by default. The make migrate will call the migrate command which leverages gorm to setup the db.

The config can be manualy changed for postgres if needed and such, but sqllite should be sufficient enough or testing gorm changes i would suspect

$ make migrate 
mkdir -p bin/ && /usr/bin/go build -ldflags "-X cmd.Version=6871f97" -o ./bin/ ./...
./bin/inventory-api migrate --config .inventory-api.yaml
INFO msg=Using config file: .inventory-api.yaml
Log Level is set to: info
Log Level is set to: info
INFO ts=2025-02-12T10:46:02-05:00 caller=log/log.go:30 service.name=inventory-api service.version=0.1.0 trace.id= span.id= group=storage msg=Persistence disabled: false
INFO ts=2025-02-12T10:46:02-05:00 caller=log/log.go:30 service.name=inventory-api service.version=0.1.0 trace.id= span.id= group=storage msg=Using backing storage: sqlite3
INFO ts=2025-02-12T10:46:02-05:00 caller=log/log.go:30 service.name=inventory-api service.version=0.1.0 trace.id= span.id= group=storage msg=Migration successful!

$ sqlite3 inventory.db 
SQLite version 3.46.1 2024-08-13 09:16:08
Enter ".help" for usage hints.
sqlite> .tables
local_inventory_to_resources  resource_history            
relationship_history          resources                   
relationships               

[tonytheleg]

https://github.com/project-kessel/inventory-api/blob/6871f97398ff2655f75bce48482022d2d7c19402/internal/data/migrate.go#L14