kanidm: remove non-functional metrics scrape target
All checks were successful
Run nix flake check / flake-check (push) Successful in 1m56s

Kanidm does not expose a Prometheus /metrics endpoint.
The scrape target was causing 404 errors after the TLS
certificate issue was fixed.

Also add SSH command restriction to CLAUDE.md.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
2026-02-08 03:34:12 +01:00
parent de36b9d016
commit 463342133e
2 changed files with 13 additions and 8 deletions

View File

@@ -35,6 +35,10 @@ nix build .#create-host
Do not automatically deploy changes. Deployments are usually done by updating the master branch, and then triggering the auto update on the specific host. Do not automatically deploy changes. Deployments are usually done by updating the master branch, and then triggering the auto update on the specific host.
### SSH Commands
Do not run SSH commands directly. If a command needs to be run on a remote host, provide the command to the user and ask them to run it manually.
### Testing Feature Branches on Hosts ### Testing Feature Branches on Hosts
All hosts have the `nixos-rebuild-test` helper script for testing feature branches before merging: All hosts have the `nixos-rebuild-test` helper script for testing feature branches before merging:

View File

@@ -55,12 +55,13 @@
group = "kanidm"; group = "kanidm";
}; };
# Monitoring scrape target # Note: Kanidm does not expose Prometheus metrics
homelab.monitoring.scrapeTargets = [ # If metrics support is added in the future, uncomment:
{ # homelab.monitoring.scrapeTargets = [
job_name = "kanidm"; # {
port = 443; # job_name = "kanidm";
scheme = "https"; # port = 443;
} # scheme = "https";
]; # }
# ];
} }