about summary refs log tree commit diff
path: root/nixpkgs/pkgs/development/tools/rakkess/default.nix
blob: 6b101e0b890cac1c708e5df04efb5e82893bde77 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
{ lib, buildGoModule, fetchFromGitHub }:

buildGoModule rec {
  pname = "rakkess";
  version = "0.5.1";

  src = fetchFromGitHub {
    owner = "corneliusweig";
    repo = pname;
    rev = "v${version}";
    sha256 = "sha256-igovWWk8GfNmOS/NbZWfv9kox6QLNIbM09jdvA/lL3A=";
  };
  vendorHash = "sha256-lVxJ4wFBhHc8JVpkmqphLYPE9Z8Cr6o+aAHvC1naqyE=";

  ldflags = [ "-s" "-w" "-X github.com/corneliusweig/rakkess/internal/version.version=v${version}" ];

  meta = with lib; {
    homepage = "https://github.com/corneliusweig/rakkess";
    changelog = "https://github.com/corneliusweig/rakkess/releases/tag/v${version}";
    description = "Review Access - kubectl plugin to show an access matrix for k8s server resources";
    mainProgram = "rakkess";
    longDescription = ''
      Have you ever wondered what access rights you have on a provided
      kubernetes cluster? For single resources you can use
      `kubectl auth can-i list deployments`, but maybe you are looking for a
      complete overview? This is what rakkess is for. It lists access rights for
      the current user and all server resources, similar to
      `kubectl auth can-i --list`.
    '';
    license = licenses.asl20;
    maintainers = with maintainers; [ jk ];
  };
}