think through consul, envconsul & consul template integration benefits vs time constraints

[noah edward hall]

C

• no way around this as you cant share env vars between groups in the same nomad job
  • neither should we continue to sidestep existing patterns
• dont just bruteforce, put your architect hat on so we dont do another detour for the 1000 time
  • haha we could just put everything in the same fkn group, but theres no shortcuts to success

T

- nirvai-core
  - [ ] haproxy edge-proxy & rev-proxy, network stats
  - [ ] consul mesh
  - [ ] vault bank
    - vault should have db engine enabled, but no db connections created
- nirvai-web
  - [ ] node bff
  - [ ] react ui
  - [ ] postgres db
  - [ ] vault (dev-only)
    - [ ] nomad should manage postgres engine connection between core-postgres and vault
      - use db connection if it exists, else create it  

A

• @see https://github.com/nirv-ai/docs/blob/main/_architecture_decision_records_/core-IaC.png
• https://github.com/hashicorp/envconsul
• https://github.com/hashicorp/consul-template
• https://github.com/haproxytech/haproxy-consul-connect
• @see hashicorp/nomad#5455