nixpkgs/pkgs/by-name/ra/rakkess/package.nix
aleksana 571c71e6f7 treewide: migrate packages to pkgs/by-name, take 1
We are migrating packages that meet below requirements:

1. using `callPackage`
2. called path is a directory
3. overriding set is empty (`{ }`)
4. not containing path expressions other than relative path (to
makenixpkgs-vet happy)
5. not referenced by nix files outside of the directory, other
than`pkgs/top-level/all-packages.nix`
6. not referencing nix files outside of the directory
7. not referencing `default.nix` (since it's changed to `package.nix`)
8. `outPath` doesn't change after migration

The tool is here: https://github.com/Aleksanaa/by-name-migrate.
2024-11-09 20:04:51 +08:00

34 lines
1.2 KiB
Nix

{ 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 ];
};
}