add note on nixops priorities
This commit is contained in:
parent
3d0fcb801e
commit
2c9369eaf3
1 changed files with 2 additions and 0 deletions
|
@ -14,6 +14,8 @@ For demo purposes until further notice, our parameters are a constant as far as
|
|||
|
||||
More important for now is having TF provider wrappers for common use cases, because that is where the application value lives
|
||||
|
||||
- kiara: i'm not sure i see TF wrapping as as important as nested deployment, fallback way if we need a TF step seems embed/use TF itself
|
||||
|
||||
On progress indication: NixOps4 is using the tracing library underneath, which offers separate events and spans (with start and end)
|
||||
|
||||
Adding JSON output is a quick fix
|
||||
|
|
Loading…
Add table
Reference in a new issue