Update ctl.erb to include clock_drift_enabled - #327
Merged
Conversation
cf-foundation-community-automation
Bot
moved this to Inbox
in Foundational Infrastructure Working Group
Because of the BPM changes that removed ctl.erb, when the ctl.erb file was remade, it didn't include the clock_drift_enabled parameter (see: https://github.com/cloudfoundry/system-metrics-release/pull/321/changes#r3581015436). This fix allows system metrics to correctly read clock_drift_enabled via ctl.erb and adds true/false unit tests. Co-authored-by: Cursor <cursoragent@cursor.com>
chombium
approved these changes
Jul 24, 2026
github-project-automation
Bot
moved this from Inbox
to Done
in Foundational Infrastructure Working Group
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
3 participants
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.
Because of the BPM changes that removed ctl.erb, when the ctl.erb file was remade, it didn't include the clock_drift_enabled parameter (see: https://github.com/cloudfoundry/system-metrics-release/pull/321/changes#r3581015436).
This fix allows system metrics to correctly read clock_drift_enabled.
Description
Please include a summary of the change.
Type of change
Testing performed?
Checklist:
mainbranch, or relevant version branchIf you have any questions, or want to get attention for a PR or issue please reach out on the #logging-and-metrics channel in the cloudfoundry slack