Volatile Configuration Warnings Package

Generates a warning when a volatile configuration rule will expire within the configured warning threshold (default 30 days). This provides advance notice to extend or replace the rule before it expires.

Solution: Review the volatile configuration rule and decide whether to extend its effectiveUntil date or remove it. If the rule is no longer needed, you can safely let it expire.

Generates a warning when a volatile configuration rule has passed its effectiveUntil date. Expired rules are no longer active and should be removed from the policy configuration.

Solution: Remove the expired volatile configuration rule from your policy. The rule is no longer having any effect and keeping it may cause confusion.

Generates a warning when a volatile configuration rule has invalid date values that cannot be parsed. This indicates a configuration error that should be corrected.

Solution: Correct the date format in the volatile configuration rule. Dates must be in RFC 3339 format (e.g., "2024-12-31T00:00:00Z").

Generates a warning when a volatile configuration rule has no effectiveUntil date set. Rules without expiration dates may accumulate over time and should be periodically reviewed.

Solution: Consider adding an effectiveUntil date to the volatile configuration rule to ensure it is reviewed periodically. Permanent exceptions should be documented with justification.

Generates a warning when a volatile configuration rule has an effectiveOn date in the future, indicating it will become active at that time.

Solution: This is informational. The volatile configuration rule will automatically become active on the effective date. No action is required unless you want to adjust the activation timing.