Skip to content

Conversation

@Ana06
Copy link
Member

@Ana06 Ana06 commented Feb 12, 2025

Ensure failed_packages.txt is always created (empty if no failures). This provides a predictable file structure for automated build scripts, allowing them to rely on the presence of this file to determine FLARE-VM installation completion.

Ensure `failed_packages.txt` is always created (empty if no failures).
This provides a predictable file structure for automated build scripts,
allowing them to rely on the presence of this file to determine FLARE-VM
installation completion.
@Ana06 Ana06 added the 💎 enhancement It is working, but it could be better label Feb 12, 2025
@Ana06 Ana06 added this to the FLARE-VM 2025 Q1 milestone Feb 12, 2025
@Ana06 Ana06 requested review from a team February 12, 2025 10:08
@Ana06 Ana06 self-assigned this Feb 12, 2025
@Ana06 Ana06 merged commit 4cd75fe into mandiant:main Feb 24, 2025
4 checks passed
Ana06 added a commit to Ana06/VM-Packages that referenced this pull request Apr 24, 2025
PR mandiant#1274 introduced the consistent creation of `failed_packages.txt` to
signal installation completion for automation. However, it also
inadvertently caused the installer to always log additional failure
information, regardless of actual package failures, because of checking
for the existence of the (now always present) file.

This commit addresses this by checking the actual count of failed
packages (`$failures.Count`). The detailed failure messages are now only
displayed when one or more packages have failed to install.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

💎 enhancement It is working, but it could be better

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant