-
Notifications
You must be signed in to change notification settings - Fork 129
Add DD_DASHBOARD_FORCE_SYNC_PERIOD environment variable #2184
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
Closed
puretension
wants to merge
8
commits into
DataDog:main
from
puretension:add-dashboard-force-sync-period-env
Closed
Changes from 2 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
760353f
Add DD_DASHBOARD_FORCE_SYNC_PERIOD environment variable Fixes #2179
puretension a43835b
trigger CI checks after labeling and milestone
puretension d7ce92c
Add DD_DASHBOARD_FORCE_SYNC_PERIOD documentation
puretension 7781b7c
Add DD_DASHBOARD_FORCE_SYNC_PERIOD documentation
puretension 5b38e10
Merge branch 'main' into add-dashboard-force-sync-period-env
puretension 1ab85a8
docs: fix duplicated configuration section and reference DD_DASHBOARD…
puretension 0fd99dd
Merge branch 'main' into add-dashboard-force-sync-period-env
tbavelier 99b5401
Update dashboard doc
tbavelier File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@puretension Thanks for putting this together! It looks good I think but it seems like this doesn't follow the same pattern as the monitors do exactly. I haven't dived too deeply into the patterns used in other crd controllers here but the Monitor controller seems to check the Monitor specific
MonitorLastForceSyncTimerather than the generic LastForceSyncTime:datadog-operator/internal/controller/datadogmonitor/controller.go
Lines 154 to 178 in 900987e
The
MonitorLastForceSyncTimeseems to be set whenever a monitor is synced. I'm not sure if having a Monitor specific variable there was intentional or not or if the maintainers care about consistency in this case but thought it'd be worthwhile to bring to your attention.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@orkhanM Great catch! You're absolutely right about the consistency issue.
Looking at the Monitor controller pattern you referenced,
I can see it uses MonitorLastForceSyncTime for the force sync check.
I'll update the Dashboard implementation to use DashboardLastForceSyncTime
to match this pattern for consistency across controllers.
Thanks for pointing this out!