From 2c9369eaf3ddbe3d5acdadbc1774eeb8ee924b4d Mon Sep 17 00:00:00 2001 From: Kiara Grouwstra Date: Tue, 4 Mar 2025 09:39:00 +0100 Subject: [PATCH] add note on nixops priorities --- meeting-notes/2025-03-03-progress-indicator-meeting.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meeting-notes/2025-03-03-progress-indicator-meeting.md b/meeting-notes/2025-03-03-progress-indicator-meeting.md index b45e498..085b9c5 100644 --- a/meeting-notes/2025-03-03-progress-indicator-meeting.md +++ b/meeting-notes/2025-03-03-progress-indicator-meeting.md @@ -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