core: sanity-check

[noahehall]

C

• alot of major changes recently, lets take a step back and review
• @see consul integration: core service mesh #24

T

• core services
  • consul good ?
  • haproxy good ?
  • vault good ?
    • update script.vault.sh to support the new vault apps-vault/src/{consul, vault}/config hierarchy

---

• update ADRs to match new status quo
  • lets move this to the lastlap ticket
• review and refactor
  • keep it dry sun

---

• scripts good ?
• docs good ?
• consul good ?
  • ensure consul.sh meets the standard set by vault.sh
  • ensure consul docs meets the standard set by vault docs
  • [ ] add a health check at docker layer once .env.auto is validated
    • push this to another ticket
  • [ ] remove bootstrap/dev mode
    • this is more of a prod task; as its not devmode just bootstrap_expect 1
    • agent: BootstrapExpect is set to 1; this is the same as Bootstrap mode.
  • [ ] add another consul instance specifically for the UI
    • this is more of a prod task

A

• @see Error: openpgp: invalid data: tag byte does not have MSB set helm/helm#2843

---

issue 1: bad certificate
we may have messed something up in the cfssl refactor
or setting the node=consul-$(hostname)
actually have no clue where we fked this one up

# resolution: if you recreate the CA , you need to retrust it in the browser
# you do not need to modify: browser.xul.error_pages.expert_bad_cert in firefox
---
An error occurred during a connection to mesh.nirv.ai:8501. Peer’s certificate has an invalid signature.

Error code: SEC_ERROR_BAD_SIGNATURE