• Type: Improvement
• Resolution: Unresolved
• Priority: Minor
• Component/s: configuration-as-code-plugin
• Labels:

  None

[JENKINS-74933] Allow ConfigurationContext to use a specific mergeStrategy

Julien Greffe created issue - 2024-11-28 08:46

Julien Greffe made changes - 2024-11-28 08:47

Assignee

New: Julien Greffe [ jgreffe ]

Julien Greffe made changes - 2024-11-28 08:55

Description

Original: The {{ConfigurationContext}} instanciation uses the {{mergeStrategy}} defined in a [system env or property|https://github.com/jenkinsci/configuration-as-code-plugin/blob/bd8aad529c49865f619982175dab7b5bfb537fb4/plugin/src/main/java/io/jenkins/plugins/casc/ConfigurationContext.java#L54]. There's currently no option to set a custom {{mergeStrategy}}, but plugins may need to execute some specific merge strategies without any system env or property defined.

New: The {{ConfigurationContext}} instanciation uses the {{mergeStrategy}} defined in a [system env or property|https://github.com/jenkinsci/configuration-as-code-plugin/blob/bd8aad529c49865f619982175dab7b5bfb537fb4/plugin/src/main/java/io/jenkins/plugins/casc/ConfigurationContext.java#L54]. When no system env or property is set, the merge strategy falls back to [errorOnConflict|https://github.com/jenkinsci/configuration-as-code-plugin/blob/652ee9bae0d9e8fe7e72755dc34a48b2218b4d99/plugin/src/main/java/io/jenkins/plugins/casc/yaml/YamlUtils.java#L37]. There's currently no option to set a custom {{{}mergeStrategy{}}}, but plugins may need to execute some specific merge strategies without any system env or property defined.

Julien Greffe made changes - 2024-11-30 09:59

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Julien Greffe made changes - 2024-11-30 09:59

Status

Original: In Progress [ 3 ]

New: In Review [ 10005 ]