[Deprecation] Fine-Grained `filetimeout` Control

[silug]

Summary

Fine-grained values for filetimeout are deprecated; warning text indicates future behavior should only distinguish cache-on/off semantics.

Evidence

• lib/puppet/defaults.rb:704 emits Puppet.deprecation_warning for non-legacy values.
• lib/puppet/defaults.rb:705 warning text: Fine grained control of filetimeouts is deprecated.
• Same warning block states future valid values are effectively 0 and 15.

Proposed OpenVox 9 Change

• Remove support for fine-grained filetimeout values beyond intended coarse behavior.
• Enforce the final supported value set and validation logic.
• Update setting docs to match final semantics.

Compatibility / Risk

• Medium risk for deployments currently using custom numeric timeout values.
• Behavior change can affect how quickly config/manifests are reloaded from disk.

Implementation Notes

• Decide final supported model explicitly:
  • Strict two-value model (0 and 15), or
  • Replacement model (0 and unlimited) if aligned with current platform strategy.
• Remove deprecation warning path once final behavior is enforced.
• Document migration from custom values to supported values.

Acceptance Criteria

• Unsupported fine-grained filetimeout values are rejected (or normalized with explicit policy).
• Deprecation warning for fine-grained control is removed.
• Reference docs and puppet config output reflect final supported behavior.

Suggested Tests

• Settings validation tests for accepted/rejected filetimeout values.
• Integration tests validating cache/reload behavior under supported values.

[binford2k]

deprecated in 09e6703

[binford2k]

this deprecates in favor of jruby timers. But if we're pulling out of the JVM, it may become useful again.

[silug]

this deprecates in favor of jruby timers. But if we're pulling out of the JVM, it may become useful again.

@binford2k that's an excellent observation. I would vote in favor of un-deprecating this feature.