You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Haven't reproduced this yet, but I realized that the for every stack that's encountered in the set of nested stacks, the tool currently tries to work with events from the latest deploy from each of them.
However those aren't necessarily from the latest deploy of the root stack. Like if you had a substack that was created once and never touched again, the code as-is would try to pull in its events even when trying to analyze the latest deploy of the root stack.
The code should instead ignore any events from any stack that precede the event that marks the start of the most recent deploy of the root stack.
The text was updated successfully, but these errors were encountered:
Haven't reproduced this yet, but I realized that the for every stack that's encountered in the set of nested stacks, the tool currently tries to work with events from the latest deploy from each of them.
However those aren't necessarily from the latest deploy of the root stack. Like if you had a substack that was created once and never touched again, the code as-is would try to pull in its events even when trying to analyze the latest deploy of the root stack.
The code should instead ignore any events from any stack that precede the event that marks the start of the most recent deploy of the root stack.
The text was updated successfully, but these errors were encountered: