You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/release-notes/ref-release-notes-breaking-changes.adoc
+2-6Lines changed: 2 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,13 +5,9 @@
5
5
This section lists breaking changes in {product}{product-version}.
6
6
7
7
[id="removed-functionality-rhidp-4572"]
8
-
== [Docs] Metrics: Document the support for exposing metrics for customers related to critical functionalities in RHDH
9
-
10
-
Breaking change.
11
-
12
-
Prom-client metrics have been removed and replaced with OpenTelemetry metrics. As a result, the metrics port has changed from 7007 to 9464. Deprecated metrics have also been removed. If you had dependencies on these, ensure your prometheus queries are updated. For further information see <link to observability/monitoring and logging docs>
13
-
8
+
== Updated monitoring and logging metrics
14
9
10
+
Prom-client metrics have been removed and replaced with OpenTelemetry metrics. As a result, the metrics port has changed from `7007` to `9464`. Deprecated metrics have also been removed. If you had dependencies on these, ensure your prometheus queries are updated. For further information, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.3/html-single/monitoring_and_logging/index#assembly-rhdh-observability[Monitoring and logging]
Copy file name to clipboardExpand all lines: modules/release-notes/ref-release-notes-deprecated-functionalities.adoc
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,16 +5,15 @@
5
5
This section lists deprecated functionalities in {product}{product-version}.
6
6
7
7
[id="deprecated-functionality-rhidp-3545"]
8
-
== Deprecation of aap plugin
8
+
== `./dynamic-plugins/dist/janus-idp-backstage-plugin-aap-backend-dynamic` plugin is deprecated
9
9
10
-
The `./dynamic-plugins/dist/janus-idp-backstage-plugin-aap-backend-dynamic` plugin has been deprecated and will be removed in the next release. You can link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html-single/using_ansible_plug-ins_for_red_hat_developer_hub/index [using Ansible plug-ins for {RHDH}] instead.
10
+
The `./dynamic-plugins/dist/janus-idp-backstage-plugin-aap-backend-dynamic` plugin has been deprecated and will be removed in the next release. You can link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html-single/using_ansible_plug-ins_for_red_hat_developer_hub/index[use Ansible plug-ins for {product-very-short}] instead.
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.
Previously, the GitHub issues plugin defaulted to using the first GitHub integration it detected for all components. This behavior made it incompatible with setups involving multiple GitHub integration hosts.
Previously, when deploying with the Helm Chart, there could be a mismatch between the Route hostname and the `baseUrl` fields added to the generated app-config ConfigMap. This could sometimes cause failure to authenticate against some providers due to an origin mismatch.
34
34
@@ -38,7 +38,7 @@ This update fixes this issue by ensuring no mismatch between those values.
38
38
39
39
40
40
[id="bug-fix-rhidp-3849"]
41
-
=== Prevent the creation of permission policies and roles when disabled
41
+
=== Disable the creation of permission policies and roles when disabling the RBAC backend plugin
42
42
43
43
Previously, disabling the RBAC backend plugin created roles and permission policies, whether the permission framework was enabled or not.
44
44
@@ -48,9 +48,9 @@ With this update, disabling the RBAC backend plugin no longer creates roles and
48
48
49
49
50
50
[id="bug-fix-rhidp-3931"]
51
-
=== Entities of repositories under a configured org in catalog-backend-module-github-org plugin are not deleted from the catalog when the imported repository is deleted from bulk imports
51
+
=== Added alert on the deletion icon during bulk imports
52
52
53
-
Before this update, repositories were added to {product-short} from various sources, such as `app-config` files or GitHub discovery. The Bulk Import plugin only tracked repositories accessible using the configured GitHub integrations. When both plugins were enabled, repositories discovered by GitHub Discovery appeared on Bulk Import pages. However, deleting these repositories from Bulk Import Jobs had no effect, as entities from discovery or `app-config.yaml` file remained in the {product-short} catalog.
53
+
Before this update, repositories were added to the {product-short} from various sources, such as `app-config` files or GitHub discovery. The Bulk Import plugin only tracked repositories accessible using the configured GitHub integrations. When both plugins were enabled, repositories discovered by GitHub Discovery appeared on Bulk Import pages. However, deleting these repositories from Bulk Import Jobs had no effect, as entities from discovery or `app-config.yaml` file remained in the {product-short} catalog.
54
54
55
55
With this update, an alert on the deletion icon notifies the user to modify the source (either the `catalog-info` within the repository or the `app-config.yaml` file if the file originates from there) to remove the catalog entity.
56
56
@@ -59,7 +59,7 @@ With this update, an alert on the deletion icon notifies the user to modify the
59
59
60
60
61
61
[id="bug-fix-rhidp-4240"]
62
-
=== [Topology] RHDH users can see tekton warnings even if they haven't configured the custom resources in k8s
62
+
=== Removed the pre-configured custom resources from the Kubernetes configuration
63
63
64
64
Before this update, the custom resources in Kubernetes configuration were pre-configured. As a result, users could see Tekton warnings without configuring the custom resources in Kubernetes.
65
65
@@ -69,27 +69,27 @@ This update removes the pre-configured custom resources from the Kubernetes conf
69
69
70
70
71
71
[id="bug-fix-rhidp-4241"]
72
-
=== RBAC Plugin is broken with latest Backstage version (1.31)
72
+
=== RBAC Plugin is broken with latest Backstage version (`1.31`)
73
73
74
-
Before this update, RBAC backend plugin broke in Backstage 1.31 with an error.
74
+
Before this update, RBAC backend plugin broke in Backstage `1.31` with an error.
75
75
76
-
This update resolves compatibility issues with RBAC backend plugin on Backstage versions 1.31 and 1.32 without displaying any errors.
76
+
This update resolves compatibility issues with RBAC backend plugin on Backstage versions `1.31` and `1.32` without displaying any errors.
=== When scaling the deployment to 3 pods + redis cache, RBAC roles are not synced
92
+
=== Resolved RBAC API inconsistency when scaling deployments to more than one pod
93
93
94
94
Before this update, scaling the deployment to more than one pod caused RBAC roles to remain unsynced, allowing only the pod that created the resource to serve it.
95
95
@@ -109,7 +109,7 @@ This update changes the parent directory that the {{require}} uses from the mono
109
109
110
110
111
111
[id="bug-fix-rhidp-5062"]
112
-
=== Error migrating techdocs-backend wrapper to export-dynamic-plugin embed-as-dependencies method
112
+
=== `suppress-native-package` and `allow-native-package` flags to handle native modules
113
113
114
114
Previously, the CLI failed with a message that native modules are not supported.
115
115
@@ -122,7 +122,7 @@ This update introduces two new CLI flags that help dynamic plugin developers han
122
122
123
123
124
124
[id="bug-fix-rhidp-5120"]
125
-
=== Huge icon when techdoc text is selected, and report a doc issue feature didn't worked [1.4]
125
+
=== Resolved the issue with text selection when reporting a TechDoc issue
126
126
127
127
Previously, the feature to report a documentation (TechDoc) issue failed. Therefore, when a user selected a text in a TechDoc, a large icon appeared instead of a tooltip button.
128
128
@@ -132,7 +132,7 @@ With this update, users can select texts when reporting a documentation (TechDoc
Previously, the `export-dynamic-plugin` failed with an error that the `stdout maxBuffer` length was exceeded.
138
138
@@ -142,7 +142,7 @@ With this update, the CLI redirects the output of the {{yarn install}} command i
142
142
143
143
144
144
[id="bug-fix-rhidp-5141"]
145
-
=== Add a flag to relax version range checks on the main package
145
+
=== Added an `--ignore-version-check` flag
146
146
147
147
Previously, exporting a plugin that has not been updated to a newer backstage version failed due to a semver check performed on dependencies of the dynamic plugin package.
Copy file name to clipboardExpand all lines: modules/release-notes/ref-release-notes-known-issues.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
This section lists known issues in {product}{product-version}.
6
6
7
7
[id="known-issue-rhidp-3396"]
8
-
== Topology plugin permission does not show up in rbac frontend ui
8
+
== Topology plugin permission is not displayed in the RBAC front-end UI
9
9
10
10
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`).
Copy file name to clipboardExpand all lines: modules/release-notes/ref-release-notes-new-features.adoc
+26-26Lines changed: 26 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,60 +5,60 @@
5
5
This section highlights new features in {product}{product-version}.
6
6
7
7
[id="enhancement-rhidp-2200"]
8
-
== Make possible to configure the path for mounting extra ConfigMaps/Secrets individually
8
+
== Added an individual `mountPath`
9
9
10
-
This update adds an additional individual mountPath for extra configmaps or secrets.
10
+
This update adds an additional individual `mountPath` for extra configmaps or secrets.
11
11
12
12
[id="feature-rhidp-3621"]
13
-
== Manage PVCs in the Operator
13
+
== `PersistentVolumeClaims` support is available
14
14
15
-
With this update, link:https://github.com/redhat-developer/rhdh-operator/blob/main/docs/configuration.md#persistentvolumeclaims[PersistentVolumeClaims (PVC)] support is available.
15
+
With this update, link:https://github.com/redhat-developer/rhdh-operator/blob/main/docs/configuration.md#persistentvolumeclaims[`PersistentVolumeClaims` (PVC)] support is available.
16
16
17
17
[id="feature-rhidp-3817"]
18
-
== Multiplatform and multiprofile Operator
18
+
== Added Configuration Profiles
19
19
20
-
With this update, there are additional link:https://github.com/redhat-developer/rhdh-operator/blob/main/docs/profiles.md[Configuration Profiles].
21
-
22
-
[id="enhancement-rhidp-4236"]
23
-
== Remove usage of the kube-rbac-proxy sidecar in the Operator deployment and switch to 'WithAuthenticationAndAuthorization' instead
24
-
25
-
This update removes the `kube-rbac-proxy` sidecar container from the RHDH Operator Pod. This sidecar container protected the operator metrics endpoint. However, the main container now provides this functionality out-of-the-box. Removing this sidecar container allows for reducing the resources required to run the Operator.
20
+
With this update, there are additional link:https://github.com/redhat-developer/rhdh-operator/blob/main/docs/profiles.md[configuration profiles].
26
21
27
22
[id="enhancement-rhidp-4384"]
28
-
== Improve use of kube-rbac-proxy
23
+
== Enhanced use of `kube-rbac-proxy`
29
24
30
25
This update removes the `kube-rbac-proxy` sidecar container from the RHDH Operator Pod. This sidecar container protected the operator metrics endpoint. However, the main container now provides this functionality out-of-the-box. Removing this sidecar container allows for reducing the resources required to run the Operator.
31
26
32
27
[id="feature-rhidp-4414"]
33
-
== RHDH Configuration value for plugin consumption
34
-
35
-
This update adds a new configuration value `flavor` to identify on which flavor of Backstage a plugin is running. Plugin authors can use this configuration value to tailor their plugins based on whether the plugins are running on RHDH, RHTAP, or Backstage.
36
-
37
-
[id="feature-rhidp-4805"]
38
-
== [Docs] Document support for RHBK v24 in RHDH
28
+
== Identifying Backstage flavor for plugins by using the `developerHub.flavor` field
39
29
40
-
With this update, you can use RHBK as an authentication provider. The Keycloak plugin will now support ingesting users and groups with RHBK. For more details, see link:https://docs.redhat.com/en/documentation/red_hat_build_of_keycloak/26.0/html-single/getting_started_guide/index#getting-started-zip-start-red-hat-build-of-keycloak[Authentication with RHBK].
30
+
With this update, you can use the `developerHub.flavor` field to identify whether plugins are running on {product-very-short}, RHTAP, or vanilla Backstage, as shown in the following example:
41
31
32
+
.`app-config.yaml` fragment with the `developerhub.flavor` field
42
33
34
+
[source,yaml]
35
+
----
36
+
developerHub:
37
+
flavor: <flavor>
38
+
----
43
39
40
+
`flavor`::
41
+
Identify the flavor of Backstage that is running. Default value: `rhdh`
44
42
45
43
46
-
[id="feature-rhidp-5156"]
47
-
== Document `backstage-plugin-catalog-backend-module-logs` change to static (1.4)
48
-
49
-
With this update, the `backstage-plugin-catalog-backend-module-logs` is enabled and converted to a static plugin improving performance and stability. The dynamic plugin was disabled in version 1.3.
44
+
[id="feature-rhidp-4805"]
45
+
== Authenticating with Red Hat Build of Keycloak
50
46
51
-
[id="feature-rhidp-5218"]
52
-
== [Docs] RHSSO 7.6 is deprecated as an authentication provider
47
+
With this update, you can use Red Hat Build of Keycloak as an authentication provider. The Keycloak plugin will now support ingesting users and groups with Red Hat Build of Keycloak. For more details, see link:https://docs.redhat.com/en/documentation/red_hat_build_of_keycloak/26.0/html-single/getting_started_guide/index#getting-started-zip-start-red-hat-build-of-keycloak[Authentication with Red Hat Build of Keycloak].
53
48
54
-
RHSSO 7.6 is deprecated as an authentication provider. You can continue to use RHSSO until the end of maintenance support. For details, see link:https://access.redhat.com/support/policy/updates/jboss_notes/#p_sso[RHSSO lifecycle dates]. As an alternative, migrate to RHBK v24.
55
49
56
50
57
51
58
52
53
+
[id="feature-rhidp-5156"]
54
+
== `backstage-plugin-catalog-backend-module-logs` is enabled
59
55
56
+
With this update, the `backstage-plugin-catalog-backend-module-logs` is enabled and converted to a static plugin improving performance and stability. The dynamic plugin was disabled in version `1.3`.
60
57
58
+
[id="feature-rhidp-5218"]
59
+
== RHSSO `7.6` is deprecated as an authentication provider
61
60
61
+
RHSSO `7.6` is deprecated as an authentication provider. You can continue to use RHSSO until the end of maintenance support. For details, see link:https://access.redhat.com/support/policy/updates/jboss_notes/#p_sso[RHSSO lifecycle dates]. As an alternative, migrate to RHBK `v24`.
0 commit comments