Skip to content

Commit 6773111

Browse files
committed
fix: update release 1.3.1 release notes
Signed-off-by: Fabrice Flore-Thébault <[email protected]>
1 parent 61809d9 commit 6773111

File tree

4 files changed

+25
-11
lines changed

4 files changed

+25
-11
lines changed

assemblies/assembly-release-notes-known-issues.adoc

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,16 @@
55
This section lists known issues in {product} {product-version}.
66

77

8+
include::modules/release-notes/snip-known-issue-rhidp-4687.adoc[leveloffset=+1]
9+
10+
811
include::modules/release-notes/snip-known-issue-rhidp-4378.adoc[leveloffset=+1]
912

1013

1114
include::modules/release-notes/snip-known-issue-rhidp-4067.adoc[leveloffset=+1]
1215

1316

14-
include::modules/release-notes/snip-known-issue-rhidp-3931.adoc[leveloffset=+1]
17+
include::modules/release-notes/snip-known-issue-rhidp-3396.adoc[leveloffset=+1]
1518

1619

1720

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
[id="known-issue-rhidp-3396"]
2+
= Topology plugin permission does not show up in rbac frontend ui
3+
4+
Some permissions that only have frontend plugins will not show up in the UI due to a requirement of needing a backend plugin to expose the permission framework's wellknow endpoint. As a workaround, you can either apply these permissions through the use of the CSV file or by directly calling the REST API of the RBAC backend plugin. Known plugins affected are Topology topology.view.read, Tekton tekton.view.read, ArgoCD argocd.view.read, and Quay quay.view.read.
5+
6+
.Additional resources
7+
* link:https://issues.redhat.com/browse/RHIDP-3396[RHIDP-3396]

modules/release-notes/snip-known-issue-rhidp-3931.adoc

Lines changed: 0 additions & 10 deletions
This file was deleted.
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
[id="known-issue-rhidp-4687"]
2+
= Updating Channel does not trigger an Operator Update
3+
4+
Administrators cannot update RHDH across channels. As a workaround, to upgrade across channels:
5+
6+
* Delete the subscription by starting `CSV: 1.y.z` from the `fast-1.y` channel.
7+
* Create a new subscription pointing to the new channel (fast or `fast-1.y+1`), using the latest CSV or a different startingCSV.
8+
* Once installed, any existing Backstage objects will be upgraded through the new operator.
9+
10+
Note, your app config may need to be adjusted as part of the rollout, if plugins have changed their name or configuration requirements.
11+
12+
13+
.Additional resources
14+
* link:https://issues.redhat.com/browse/RHIDP-4687[RHIDP-4687]

0 commit comments

Comments
 (0)