Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Post-Upgrade Snapshot and Report Generation Skipped for Firewalls #96

Closed
cdot65 opened this issue Feb 25, 2024 · 0 comments · Fixed by #97
Closed

Post-Upgrade Snapshot and Report Generation Skipped for Firewalls #96

cdot65 opened this issue Feb 25, 2024 · 0 comments · Fixed by #97
Assignees
Labels
bug Something isn't working

Comments

@cdot65
Copy link
Owner

cdot65 commented Feb 25, 2024

Describe the bug

After completing firewall upgrades, the post-upgrade process is expected to take snapshots and generate diff reports. However, these steps are being skipped, seemingly due to the code block that bypasses the report generation process if settings.yaml is not found. This results in missing post-upgrade snapshots and reports, which are crucial for verifying upgrade success and diagnosing issues.

To Reproduce

Steps to reproduce the behavior:

  1. Execute the firewall upgrade script without a settings.yaml file in the working directory.
  2. Complete the firewall upgrade process.
  3. Observe that the post-upgrade snapshots and diff report generation steps are skipped.

Expected behavior

Regardless of the presence of settings.yaml, post-upgrade snapshots and reports should be generated to ensure that the upgrade's effects can be reviewed and verified.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: macOS, Linux, WSL2

Additional context

The issue seems to stem from the conditional check for settings.yaml presence, which also considers the snapshot settings within the file. If settings.yaml is not found, the process to generate snapshots, diff, and PDF reports is entirely skipped. A proposed solution is to decouple the snapshot and report generation from the settings.yaml presence and its snapshot settings, ensuring these post-upgrade steps are always executed.

@cdot65 cdot65 added the bug Something isn't working label Feb 25, 2024
@cdot65 cdot65 self-assigned this Feb 25, 2024
@cdot65 cdot65 linked a pull request Feb 25, 2024 that will close this issue
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant