Is there anyway to cache the deep merged stack yam...
# atmosr
RB
03/05/2026, 5:48 AMIs there anyway to cache the deep merged stack yaml to save time when running subsequent commands like plan/apply? Hoping to run something like
atmos describe components > deepmerge.yamlatmos plan xyz -s ue1-dev --cached-deepmerge-yaml deepmerge.yamla
Andriy Knysh (Cloud Posse)
03/05/2026, 5:49 AMhow much time you think you can save?
is it slow for you?
Andriy Knysh (Cloud Posse)
03/05/2026, 5:49 AMAndriy Knysh (Cloud Posse)
03/05/2026, 5:50 AMmaybe run it with
--heatmape
Erik Osterman (Cloud Posse)
03/05/2026, 5:55 AMWe've done a TON of performance enhancements, so it would be helpful to know what's taking the time
Erik Osterman (Cloud Posse)
03/05/2026, 5:56 AMI think you can run that profiling and share the prof file with @Andriy Knysh (Cloud Posse)
r
RB
03/05/2026, 12:54 PMOne issue is that we're stuck on an old version 1.168 due to some stack yaml shenanigans so we need to get that fixed before we can migrate... Sigh
RB
03/05/2026, 12:56 PMThe other issue is running those atmos commands subsequently too many times, like running generate tfvars and such for trivy and other sast like scans, so it was better for us to reorder those steps. There's still some things we cannot reorder our selves out and caching would help. We'll try to upgrade again and see what our heatmap looks like. Thank you
e
Erik Osterman (Cloud Posse)
03/05/2026, 12:59 PMAh yes! That is before we released these improvements. I think there were 10x performance gains
Erik Osterman (Cloud Posse)
03/05/2026, 1:00 PMWhat are the YAML issues you are running into? We don't intend for any breaking changes between minor versions
Erik Osterman (Cloud Posse)
03/05/2026, 1:01 PMThere could be minor tweaks we can do to make that easier for you to upgrade, so please share specifics and we can see what we can do
r
RB
03/05/2026, 1:10 PMThanks Eric, I'll share today. Maybe i can claude up a small poc
👍 1
2 Views