Generate Django forms from deployment options
fricklerhandwerk
deleted branch use-config-module from fricklerhandwerk/Fediversity
2025-05-12 09:50:01 +02:00
actually use the typed configuration in deployment
categorize issue tracker
pydantic enum warning: Expected
enum but got str
This needs to be fixed here: a6acd5214a/src/datamodel_code_generator/parser/base.py (L1015)
actually use the typed configuration in deployment
fricklerhandwerk
pushed to use-config-module at fricklerhandwerk/Fediversity
2025-05-09 12:46:51 +02:00
fricklerhandwerk
created branch use-config-module in fricklerhandwerk/Fediversity
2025-05-09 12:45:44 +02:00
fricklerhandwerk
pushed to use-config-module at fricklerhandwerk/Fediversity
2025-05-09 12:45:44 +02:00
Introduce test for deploying all services with
nixops4 apply
TODOs from verbal sync:
- modularise all test parameters, it's the main barrier to readability
- try to fold the
fakenode into a nested derivation (not a blocker) - try to address the minor…
Introduce test for deploying all services with
nixops4 apply
It's created in the unpacking subtest defined in the test module generator.
Introduce test for deploying all services with
nixops4 apply
It would be a lot simpler and much more idiomatic if you enabled acme right there in the module. Then we wouldn't need the extra file, which makes it harder to track down what's happening.
Introduce test for deploying all services with
nixops4 apply
Why not copy it to the final location directly?
Introduce test for deploying all services with
nixops4 apply
Maybe worth mentioning here that since nixops4 apply operates on a flake, the tests take this repository's flake as a template, and this also why there are some dummy files that will be overwritten inside the test. Although why are we even keeping the unused files? They could just as well be created during the test, no?