-
-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
typeguard exception with deployment.keys #1570
Comments
I'll take a look tomorrow morning. |
Any update on this? |
Sorry, completely lost track of this :( Can you try #1572 ? |
Is there an easy way to get the a flake input with your contribution? |
|
That did not fix the problem. |
Sorry then, I'm temporarily out of ideas. I'll have to look at it closer later. For now you should be able to comment out this line: Line 168 in 2cfc2cb
|
Maybe we should do that for now and push a patch release? nixops has been broken in nixpkgs for quite a while now, and while it is possible to use a pinned version it is annoying and requires every user to find out what is happening on their own. |
I've opened #1573, which solves this for me, but it would be nice with more testing. |
hope this isn't too offtopic but I am trying to use these patches, but with a flake like this: {
inputs = {
nixpkgs.url = "nixpkgs/nixos-unstable";
flake-utils.url = "github:numtide/flake-utils";
nixops.url = "github:talyz/nixops/mapping-types";
nixops.inputs.nixpkgs.follows = "nixpkgs";
};
outputs = { self, nixpkgs, flake-utils, nixops, ... }:
{
nixopsConfigurations.default = {
inherit nixpkgs;
network.storage.legacy.databasefile = "~/.nixops/deployments.nixops";
network.enableRollback = true;
};
} // flake-utils.lib.eachDefaultSystem (system:
let
pkgs = nixpkgs.legacyPackages.${system};
nixops-pkgs = nixops.packages.${system};
in {
devShell = pkgs.mkShell {
buildInputs = [
pkgs.nix
nixops-pkgs.default
];
};
formatter = nixpkgs.legacyPackages.${system}.nixpkgs-fmt;
});
} I just get
wish something like this would work ^^ #1324 (comment) |
Yes, that should be because the hetzner plugin is missing. A somewhat easy way to test this is to override NixOps' |
This has been broken in For those who need to deploy now an easy workaround is using nixops from 23.05 |
#1573 is the fix, I'll poke Robert about it. |
With recent nixops, using keys results in the error:
typeguard.TypeCheckError: value of key 'test' of nixops.resources.ResourceEval is not an instance of nixops.backends.KeyOptions
Full exception
flake.nix
The text was updated successfully, but these errors were encountered: