Skip to content
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

Limit usage of YAML Serializer #3796

Merged
merged 2 commits into from
Feb 4, 2022
Merged

Conversation

geoand
Copy link
Contributor

@geoand geoand commented Feb 2, 2022

Description

The YAML serializer is mainly used in order to parse the kubernetes config.
This change should not have any functional effect whatsoever, but it paves the way for what I have in mind as a follow-up, which is to provide a public method that allows for clearing out the YAMLMapper (the reasoning being that this is a very heavy object that most likely is only used when the client is first booted).

@manusa manusa added this to the 5.12.1 milestone Feb 2, 2022
@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 2, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

@metacosm
Copy link
Collaborator

metacosm commented Feb 2, 2022

One usage of the YAML parser that needs to be taken into account is that people very often load an initial/skeleton resource from YAML and then populate it with values at runtime, so this use case needs to be taken into account as well.

Copy link
Contributor

@shawkins shawkins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@manusa manusa merged commit 5d5ff8e into fabric8io:master Feb 4, 2022
@geoand geoand deleted the yaml-serializer branch February 11, 2022 07:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants