docs(bounty): proposal for feature to hide annotations on secrets in …

…UI (argoproj#15699) * docs(bounty): proposal for feature to hide annotations on secrets in the UI Signed-off-by: Michael Crenshaw <[email protected]> * fix file location Signed-off-by: Michael Crenshaw <[email protected]> --------- Signed-off-by: Michael Crenshaw <[email protected]>
ymktmk · Oct 29, 2023 · 90e16e7 · 90e16e7
1 parent 4eb1440
commit 90e16e7
Showing 1 changed file with 23 additions and 0 deletions.
diff --git a/docs/proposals/feature-bounties/hide-annotations.md b/docs/proposals/feature-bounties/hide-annotations.md
@@ -0,0 +1,23 @@
+# Proposal: Allow Hiding Certain Annotations in the Argo CD Web UI
+
+Based on this issue: https://github.com/argoproj/argo-cd/issues/15693
+
+Award amount: $100
+
+## Solution
+
+!!! note
+     This is the proposed solution. The accepted PR may differ from this proposal.
+
+Add a new config item in argocd-cm:
+
+```yaml
+hide.secret.annotations: |
+- openshift.io/token-secret.value
+```
+
+This will hide the `openshift.io/token-secret.value` annotation from the UI. Behind the scenes, it would likely work the
+same way as the `last-applied-configuration` annotation hiding works: https://github.com/argoproj/gitops-engine/blob/b0fffe419a0f0a40f9f2c0b6346b752ed6537385/pkg/diff/diff.go#L897
+
+I considered whether we'd want to support hiding things besides annotations and in resources besides secrets, but
+having reviewed existing issues, I think this narrow feature is sufficient.