-
Notifications
You must be signed in to change notification settings - Fork 57
Open
Labels
kind/bugBug related issueBug related issue
Description
Describe the bug
If CasC is used to configure Datadog plugin, settings which are not explicitly set in CasC will not be changed, so settings from existing config (from global configuration page) will persist after applying CasC.
To Reproduce
Steps to reproduce the behavior:
- Setup CasC config w/o some optional settings for Datadog plugin (w/o
enableCiVisibilityfor example)
datadogGlobalConfiguration:
emitSecurityEvents: true
emitSystemEvents: true
hostname: "host"
reportWith: "DSD"
targetHost: "localhost"
targetPort: "8125"
targetTraceCollectionPort: "8126"
- Apply CasC config
- Go to global configuration
- Ensure that Datadog plugin has default values in all unset settings (CI Visibility is disabled)
- Change on of unset settings via UI on global configuration page (enable CI Visibility for example)
- Apply and save changes.
- Apply CasC config again
- Go to global configuration
- See that settings are not changed (CI Visibility is still enabled)
Expected behavior
After applying CasC I'd expect overriding unset settings with default values. In other words I want to make sure that if CasC config is used, it is the single source of truth for Datadog plugin settings.
Environment and Versions (please complete the following information):
CasC plugin: 1512.vb_79d418d5fc8
datadog plugin: 5.0.0
Jenkins LTS: 2.361.1
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/bugBug related issueBug related issue
