openbao-agent invalid config with no templates defined #254
Labels
No labels
Compat/Breaking
Difficulty/Architectural
Difficulty/Easy
Difficulty/Hard
Help Wanted
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Security
Silenced Alert
Status/Abandoned
Status/Blocked
Status/Need More Info
Status/Postponed
Tracking Issue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: afnix/infra#254
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Using the openbao-agent module without defining any templates seems to lead to a config that the agent cannot parse (failing to initialize):
Consider using
services.vault-agent
from nixpkgs instead ofservices.openbao-agent
from https://git.lix.systems/the-distro/systemd-openbao.The module in https://git.lix.systems/the-distro/systemd-openbao (or rather https://github.com/numtide/systemd-vaultd) exists, because at the time there simply was no module for that in nixpkgs yet.
See
The timing on this is just funny, because you happen to encounter this a few weeks after https://github.com/NixOS/nixpkgs/issues/420208 and a few days after https://github.com/NixOS/nixpkgs/pull/431031 was opened, but not merged yet.
I am also in the process of renaming
services.vault-agent
toservices.openbao-agent
for various reasons in nixpkgs, but we will see how that goes. For now, the main difference is that you need to setservices.vault-agent.instances.<name>.package = pkgs.openbao
.And you will have to bump your nixpkgs input for this once.