Skip to content

Commit 7be7c2f

Browse files
committed
regenerate release notes from JIRA to pull in new issue rhidp-4780 and apply minor formatting changes
Signed-off-by: Nick Boldt <[email protected]>
1 parent 4a8f61e commit 7be7c2f

File tree

3 files changed

+25
-19
lines changed

3 files changed

+25
-19
lines changed

modules/release-notes/ref-release-notes-deprecated-functionalities.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ The `./dynamic-plugins/dist/janus-idp-backstage-plugin-aap-backend-dynamic` plug
1616
[id="deprecated-functionality-rhidp-4913"]
1717
== Audit log rotation is deprecated
1818

19-
With this update, you can evaluate your platform's log forwarding solutions to align with your security and compliance needs. Most of these solutions offer configurable options to minimize the loss of logs in the event of an outage.
19+
With this update, you can evaluate your platform&#39;s log forwarding solutions to align with your security and compliance needs. Most of these solutions offer configurable options to minimize the loss of logs in the event of an outage.
2020

2121

2222
.Additional resources

modules/release-notes/ref-release-notes-known-issues.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@ This section lists known issues in {product} {product-version}.
77
[id="known-issue-rhidp-5344"]
88
== Multi-Attached error for Volume (PVC)
99

10-
Currently, when deploying {product-short} using the Helm Chart, two replicas cannot run on different cluster nodes. This might also affect the upgrade from 1.3 to 1.4.0 if the new pod is scheduled on a different node.
11-
10+
Currently, when deploying {product-short} using the Helm Chart, two replicas cannot run on different cluster nodes. This might also affect the upgrade from 1.3 to 1.4.0 if the new pod is scheduled on a different node.
11+
1212
A possible workaround for the upgrade is to manually scale down the number of replicas to 0 before upgrading your Helm release. Or manually remove the old {product-short} pod after upgrading the Helm release. However, this would imply some application downtime. You can also leverage a Pod Affinity rule to force the cluster scheduler to run your {product-short} pods on the same node.
1313

1414

@@ -18,7 +18,7 @@ A possible workaround for the upgrade is to manually scale down the number of re
1818
[id="known-issue-rhidp-3396"]
1919
== Topology plugin permission is not displayed in the RBAC front-end UI
2020

21-
Permissions associated only with front-end plugins do not appear in the UI because they require a backend plugin to expose the permission framework's well-known endpoint. As a workaround, you can apply these permissions by using a CSV file or directly calling the REST API of the RBAC backend plugin. Affected plugins include Topology (`topology.view.read`), Tekton (`tekton.view.read`), ArgoCD (`argocd.view.read`), and Quay (`quay.view.read`).
21+
Permissions associated only with front-end plugins do not appear in the UI because they require a backend plugin to expose the permission framework&#39;s well-known endpoint. As a workaround, you can apply these permissions by using a CSV file or directly calling the REST API of the RBAC backend plugin. Affected plugins include Topology (`topology.view.read`), Tekton (`tekton.view.read`), ArgoCD (`argocd.view.read`), and Quay (`quay.view.read`).
2222

2323

2424
.Additional resources

modules/release-notes/ref-release-notes-new-features.adoc

Lines changed: 21 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -27,26 +27,32 @@ This update removes the `kube-rbac-proxy` sidecar container from the RHDH Operat
2727
[id="feature-rhidp-4414"]
2828
== Identifying Backstage flavor for plugins by using the `developerHub.flavor` field
2929

30-
With this update, you can use the `developerHub.flavor` field to identify whether plugins are running on {product-very-short}, {rhtap-very-short}, or vanilla Backstage, as shown in the following example:
31-
32-
.`app-config.yaml` fragment with the `developerhub.flavor` field
33-
34-
[source,yaml,subs="+quotes"]
35-
----
36-
developerHub:
37-
flavor: <flavor>
38-
----
39-
40-
`flavor`::
30+
With this update, you can use the `developerHub.flavor` field to identify whether plugins are running on {product-very-short}, {rhtap-very-short}, or vanilla Backstage, as shown in the following example:
31+
32+
.`app-config.yaml` fragment with the `developerhub.flavor` field
33+
34+
[source,yaml,subs=&#34;+quotes&#34;]
35+
----
36+
developerHub:
37+
flavor: &lt;flavor&gt;
38+
----
39+
40+
`flavor`::
4141
Identify the flavor of Backstage that is running. Default value: `rhdh`
4242

4343
[id="feature-rhidp-4419"]
4444
== Ability to manage Persistent Volume Claim (PVCs) in {product-very-short} Operator
4545

46-
You can now mount directories from pre-created PersistentVolumeClaims (PVCs) using the `spec.application.extraFiles.pvcs` field, while configuring RHDH Operator.
47-
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/{product-version}/html-single/configuring/index#configuring-the-deployment[Configuring {product} deployment when using the Operator].
46+
You can now mount directories from pre-created PersistentVolumeClaims (PVCs) using the `spec.application.extraFiles.pvcs` field, while configuring RHDH Operator.
47+
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/{product-version}/html-single/configuring/index#configuring-the-deployment[Configuring {product} deployment when using the Operator].
4848

4949

50+
[id="feature-rhidp-4780"]
51+
== [Docs] Document per-ConfigMap/Secret configuration of mountPath
52+
53+
(Added the link to this document to the Release Notes item which was added on 1.4)
54+
https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.4/html/release_notes/new-features#enhancement-rhidp-2200
55+
5056
[id="feature-rhidp-4805"]
5157
== Authenticating with {rhbk-brand-name}
5258

@@ -55,8 +61,8 @@ With this update, you can use {rhbk-brand-name} as an authentication provider. T
5561
[id="feature-rhidp-4806"]
5662
== Ability to install third-party plugins in {product-very-short}
5763

58-
You can now install third-party plugins in {product} without rebuilding the {product-very-short} application.
59-
64+
You can now install third-party plugins in {product} without rebuilding the {product-very-short} application.
65+
6066
For more information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/{product-version}/html-single/installing_and_viewing_plugins_in_red_hat_developer_hub/index#assembly-install-third-party-plugins-rhdh[Installing third-party plugins in {product}].
6167

6268
[id="feature-rhidp-5156"]

0 commit comments

Comments
 (0)