marcel/argo-cd
1
0
Fork 0
mirror of https://github.com/argoproj/argo-cd.git synced 2026-02-20 01:28:45 +01:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix version reference for logs UI fix (#10245)

Browse Source 
Signed-off-by: CI <michael@crenshaw.dev>
This commit is contained in:
Michael Crenshaw
2022-08-09 16:57:27 -04:00
committed by GitHub
parent 0ce705471e
commit 15965b8262
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
CHANGELOG.md
View File

@@ -186,9 +186,9 @@ your feedback and introduced additional access control settings that control acc
#### Pod Logs UI #### Pod Logs UI
Since 2.4.7, the LOGS tab in pod view is visible in the UI only for users with explicit allow get logs policy. Since 2.4.9, the LOGS tab in pod view is visible in the UI only for users with explicit allow get logs policy.
#### Known pod logs UI issue prior to 2.4.7 #### Known pod logs UI issue prior to 2.4.9
Upon pressing the "LOGS" tab in pod view by users who don't have an explicit allow get logs policy, the red "unable to load data: Internal error" is received in the bottom of the screen, and "Failed to load data, please try again" is displayed. Upon pressing the "LOGS" tab in pod view by users who don't have an explicit allow get logs policy, the red "unable to load data: Internal error" is received in the bottom of the screen, and "Failed to load data, please try again" is displayed.

4
docs/operator-manual/upgrading/2.3-2.4.md
View File

@@ -153,9 +153,9 @@ p, role:test-db-admins, logs, get, staging-db-admins/*, allow
### Pod Logs UI ### Pod Logs UI
Since 2.4.7, the LOGS tab in pod view is visible in the UI only for users with explicit allow get logs policy. Since 2.4.9, the LOGS tab in pod view is visible in the UI only for users with explicit allow get logs policy.
### Known pod logs UI issue prior to 2.4.7 ### Known pod logs UI issue prior to 2.4.9
Upon pressing the "LOGS" tab in pod view by users who don't have an explicit allow get logs policy, the red "unable to load data: Internal error" is received in the bottom of the screen, and "Failed to load data, please try again" is displayed. Upon pressing the "LOGS" tab in pod view by users who don't have an explicit allow get logs policy, the red "unable to load data: Internal error" is received in the bottom of the screen, and "Failed to load data, please try again" is displayed.