I recall we talked about a switch that would expla...
# atmos-devr
RB
03/15/2026, 3:37 AMI recall we talked about a switch that would explain where every key came from post deep merge. This should give us that via
--explaine
Erik Osterman (Cloud Posse)
03/15/2026, 3:54 AMwe have a
--provenancer
RB
03/15/2026, 3:55 AMGasp! Is that the same thing??
e
Erik Osterman (Cloud Posse)
03/15/2026, 3:55 AMI believe so.
Erik Osterman (Cloud Posse)
03/15/2026, 3:55 AMIt shows which file influence any value.
r
RB
03/15/2026, 3:56 AMOh maaaaaan no way, i had no idea. Thank you, ill use provenance then
RB
03/15/2026, 3:57 AMHmm wait, provenance doesn't show the full trace tho
RB
03/15/2026, 3:57 AMSo if you have 4 different catalogs that overwrite the same key, you wont know from provenance
RB
03/15/2026, 3:58 AMYoud only know the winner
RB
03/15/2026, 3:58 AMWhereas with explain, it will show the full import chain
e
Erik Osterman (Cloud Posse)
03/15/2026, 4:09 AMthen maybe it should be
--provenance-chainErik Osterman (Cloud Posse)
03/15/2026, 4:12 AMone of the design goals with
atmos describeErik Osterman (Cloud Posse)
03/15/2026, 4:12 AMCleanShot 2026-03-14 at 23.12.47@2x.png
Erik Osterman (Cloud Posse)
03/15/2026, 4:14 AMWhat about
--provenance=trace--provenance=fullr
RB
03/15/2026, 4:15 AMYeah i like that a lot
e
Erik Osterman (Cloud Posse)
03/15/2026, 4:15 AM(I thought you were on vacation?!)
r
RB
03/15/2026, 4:15 AMMaybe the yaml oitput for the full/trace would be a list of imports that set the key and the last one would win
RB
03/15/2026, 4:16 AMI am lol but i am throwing out a lot of ideas to copilot/claude for projects i love
❤️ 1
2 Views