Repository navigation
fix: generate all reference YAML settings in v1.6.1 installer - #14
Merged
Merged
Conversation
3 of 8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The v1.6.0 installer generated watchdog-config.yaml without five active fields from watchdog-config.yaml.example: lifecycle_detection.enabled, lifecycle_detection.correlation_window_seconds, restart_recovery_stability_seconds, alert_on_recovery and ignored_container_events. The installed Python defaults covered the first four at runtime, but operators could not see/tune them in YAML. Both IAD1 and EU1 confirm the four omissions (read-only inspection).
Fix
Validation (non-destructive)
Release gate
Targets release/v1.6.1; after development CI and review this may be integrated. Keep release PR #12 DRAFT for additional changes. Do NOT tag, publish or deploy v1.6.1.