Fix #2510: Yaml containing aliases rejected due to FasterXML bug

[rohanKanojia]

Fix #2510
Modify the way we deserialize Yaml objects. Load them into raw HashMap
using SnakeYAML and then use Jackson to convert them to JSON and finally
the required object

Description

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change
• Chore (non-breaking change which doesn't affect codebase;
  test, version modification, documentation, etc.)

Checklist

• Code contributed by me aligns with current project license: Apache 2.0
• I Added CHANGELOG entry regarding this change
• I have implemented unit tests to cover my changes
• I have added/updated the javadocs and other documentation accordingly
• No new bugs, code smells, etc. in SonarCloud report
• I tested my code in Kubernetes
• I tested my code in OpenShift

[manusa]

Since we want a consistent, deterministic behavior maybe instead of a fallback approach we could try something like:

Deserialization

• Load YAML into an untyped object using SnakeYaml.
• Serialize YAML into JSON
• Use Jackson to deserialize the JSON into the final type

This way we will always take advantage of custom deserializers specified with Jackson Annotations.

Serialization
No bug was reported for this process. I would really don't touch this.

• Object is serialized into YAML using Jackson

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication

[manusa]

[merge]