Bug 2072203

Summary:	Don't Mutate Extension Objects for Translations
Product:	OpenShift Container Platform	Reporter:	Andrew Ballantyne <aballant>
Component:	Management Console	Assignee:	Andrew Ballantyne <aballant>
Status:	CLOSED DEFERRED	QA Contact:	Yadan Pei <yapei>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.11	CC:	aos-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-03-09 01:16:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2063753
Bug Blocks:

Description Andrew Ballantyne 2022-04-05 19:09:38 UTC

When we call useExtensions it parses the properties of the extension for "%...%" property values. Once it finds this, it mutates in place the value with the translated value for the current selected language.

In #2063753 we changed it to manage translating the same fashion but holding onto the translation key so it can be applied multiple times as each language change happens. This however needed to be packported, so the solution kept the mutations.

This ticket should serve to properly translate once and return a mutated extension object in order to properly help the rest of the code base handle referencial checks properly as the language changes.

Comment 2 Andrew Ballantyne 2022-06-14 17:05:06 UTC

Insufficient time is left in the release -- this could have performance issues. Will bump to the next release.

Comment 3 Shiftzilla 2023-03-09 01:16:47 UTC

OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira.

https://issues.redhat.com/browse/OCPBUGS-9208