DevOps Community Sponsored by Cloud Posse

SweetOps

image.png

Question. I'm using `atmos terraform plan --all` in GitHub action, but noticing the following in GitHub Summary. Is this expected?

This way I'll have more info in the event I need to submit a ticket.

<https://github.com/cloudposse/atmos/issues/2397|Bug: CI hooks fire only once in `--all` mode, producing summary for last component only · Issue #2397 · cloudposse/atmos>

i suspect it might be overriding the output

I'm also wondering something. When running `--all`, does it honor component dependencies and run in the defined order?

<@UB2EH889X> dumb question of the day! I need to write a GitHub action that does the following:
• plans all components in order of dependency
• ensure plan files are available as both binary and JSON
I'm fiddling around with the stuff, but figured I'd ask before I reinvent the wheel :see_no_evil:

Yeah, you really need the plan file support that we are building into Atmos native CI.

Um I really would hate to see you build something custom because it's definitely not worth investing in.

Most of the work is already done for that plan file storage, but we are tied up in other work.

If you'd like to help us get it over the line, I could ask <@UBED6CS1Z> where it was left off.

As for the order of dependencies, that's also something we need to fix, but I think the scope is greater than we anticipated to do it right.

<@U080A43T0BF> have you thought any more about the ordered applies?

just bought $100 AI subscription :see_no_evil: will start burning tokens on PRD for parallel deployments