Cannot get real configmap data, if configmap's data have same Key name.

[kyleli666]

Describe the bug
Cannot get real configmap content, if configmaps having same Key name.

To Reproduce
Steps to reproduce the behavior:

1. create some configmaps with same key names but different value
   

2. Click on a configmap to see its data content

3. Switch to another configmap to see that data content, but you'll see the content is still the first configmap's

Expected behavior
See the real content of the configmap I click on.

Environment (please complete the following information):

• Lens Version: lens 2023.3.62352, extension api 6.4.3
• OS: Windows
• Installation method (e.g. snap or AppImage in Linux): windows installation

[jw-maynard]

Any timeline on this bug? It could be a dangerous bug if you were to save the wrong configmap back using the save button in the UI.

[UnleashSpirit]

Hello,
I confirm the bug, really disturbing as you don't see it the firsts times

[Noksa]

Encountered the same.
Does it work as expected in one of old versions? Or this bug exists in all versions?

[hardenchant]

I confirm it too. Had a dumb moments with that bug :((

[kyleli666]

Encountered the same. Does it work as expected in one of old versions? Or this bug exists in all versions?

It works in extension api 6.2.5

[plevart]

I have already lost some important config data because of this bug. Very dangerous. I had to add comments to the top of the entries to remind me which content I'm actually observing. You have to close connection to k8s cluster and re-open it to flush the cache and get correct content. Please fix this. Thanks.

[plevart]

Update: It seems that 6.5.0-alpha.3 fixes this. No mention in the CHANGES files though.

[philbert101]

config map bug 6.4.3 GUI property not matches yaml file

[tomer-ds]

Big +1!!!! Very disturbing and dangerous
👍🏼

[Noksa]

In the name of all that's holy, why hasn't this been fixed yet?

[tomer-ds]

There is clearly an alpha with a fix... just hoping beyond hope that it is released quickly

[kukkjanos]

This is a serious error that would be treated as a high priority.

[aleksfront]

Until bugfix created: there is a workaround using page reload cmd+r to clear up stale values. Also, it relates to details panel:

• if the details open, then toggling between the config-maps displays the correct information
• if the details closed in-between viewing the config-maps, that we are "stuck" in the last shown ConfigMap even on latest version (6.5.0)

config.maps.stale.data.mov

[plevart]

So this bug is not important to you and so it was removed from further milestones?

I'm trying to use 6.5alpha3, but it keeps self-updating back to 6.4.xx releases each time I restart the app. Very painful. Is it possible to stop this nonsense? 6.5 should not auto-downgrade to 6.4 regardless of release status. Please!

[kyleli666]

@plevart you can set the update channel to Alpha in preference.

Even 6.5alpha3 still sometimes has bug in this issue, and I also found the pod log view is not stable.

[panuhorsmalahti]

Reproduced on 2023.4.141316-latest

[panuhorsmalahti]

I couldn't reproduce this on 6.5.0-alpha.6.

[aleksfront]

@kyleli666 Can you elaborate pod log view is not stable?

[kyleli666]

Hi @aleksfront
In 6.5.0-alpha.3, the pod log view is usually visible, but when looking through the logs this screen flashes out from time to time.

[panuhorsmalahti]

Closing this issue, lets re-open if it occurs on a Lens release with 6.5.0.