nixops-aws
nixops-aws copied to clipboard
TODO - [ ] Rebase off #162 commits onto master. - [ ] Remove `default.nix` and friends
This just puts the check back to how it was when the code was originally written, it is at least *more* correct than before.
I submitted a PR: https://github.com/NixOS/nixops-aws/pull/1 which allows to use profiles with assumeRole and MFA, features which are not supported by the old boto. This also helps with effort to move...
I've tried using the s3 remote backend below ``` network.storage.s3 = { profile = "root"; region = "us-east-1"; bucket = "main-nixops-state"; key = "personal.nixops"; kms_keyid = "166c5cbe-b827-4105-bdf4-a2db9b52efb4"; }; ``` however...
The README says https://github.com/NixOS/nixops-aws/blame/ce9e0ae63981c5c727a688eec5c314e38694eba2/README.md#L31 ``` Documentation for the `nixops-aws` plugin is in the [nixops repo](https://github.com/NixOS/nixops) ``` but the manual linked from https://github.com/NixOS/nixops, which is currently https://hydra.nixos.org/build/115931128/download/1/manual/manual.html, does not document any...
`nix-shell` failed with Nixpkgs from unstable channel (`nixpkgs-21.11pre317460.a54d2e72e28`) because of an error with `mypy` v0.770: ``` Processing /private/tmp/nix-build-python3.9-mypy-0.770.drv-0/mypy-0.770 Created temporary directory: /private/tmp/nix-build-python3.9-mypy-0.770.drv-0/pip-req-build-crybcke8 Added file:///private/tmp/nix-build-python3.9-mypy-0.770.drv-0/mypy-0.770 to build tracker '/private/tmp/nix-build-python3.9-mypy-0.770.drv-0/pip-req-tracker-2damr_g5' Running setup.py...
`nixops destroy -d mydeployment` outputs: ``` fooResource..................> deleting EC2 security group `fooResource' ID `None'... * fooResource: EC2ResponseError: 400 Bad Request MissingParameterThe request must contain the parameter groupName or groupId ```...
Building on nixos 21.11 from current master (8390088) I get: ``` Skipping optional fixer: idioms Skipping optional fixer: set_literal Skipping optional fixer: ws_comma regex_3/_regex.c: In function ‘folded_char_at’: regex_3/_regex.c:9897:9: warning: variable...
Given that the RDS database instance is considered as a resource and not a machine, would it be possible to introduce the stop/start operations? If yes, we can also consider...
The deploy process will hang in https://github.com/NixOS/nixops/blob/master/nixops/backends/ec2.py#L543 i.e waiting for the device to be visible in the device filesystem due to the difference in nvme device names.