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-deprecated-functionalities.adoc
+13-2Lines changed: 13 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,9 +7,9 @@ This section lists deprecated functionalities in {product} {product-version}.
7
7
[id="deprecated-functionality-rhidp-6215"]
8
8
== The Topology-specific permission `topology.view.read` is removed
9
9
10
-
Previously, the Topology plugin used `topology.view.read` permission to control access. Users were unable to configure Topology permissions via RBAC UI. With this update, users can configure Kubernetes plugin permissions via RBAC UI that now governs the access to Topology plugin. You can now use Kubernetes plugin permissions `kubernetes.clusters.read` and `kubernetes.resources.read` for Topology plugin, as topology-specific permission `topology.view.read` is removed.
10
+
Previously, the Topology plugin used `topology.view.read` permission to control access. Users were unable to configure Topology permissions using the RBAC UI. With this update, users can configure Kubernetes plugin permissions using the RBAC UI, which now governs the access to the Topology plugin. You can now use Kubernetes plugin permissions `kubernetes.clusters.read` and `kubernetes.resources.read` for the Topology plugin, as the topology-specific permission `topology.view.read` is removed.
11
11
12
-
If you are using csv permission file, update the following line:
12
+
If you are using a CSV permission file, update the following line:
== Deprecation of dynamic imports with `import(...)`
33
+
34
+
The use of dynamic imports with `import(...)` has been deprecated and is no longer supported. The Backstage CLI supports native ESM in Node.js code, giving access to the importing of ESM-only packages. Therefore, you must now use `require(...)` as typeof `import(...)` when working with ESM or CommonJS packages.
=== Floating Action Button (FAB) positioned in the 'Bottom-Left' slot on {product-short}
11
23
@@ -21,7 +33,7 @@ With this update, the FAB's position is adjusted to render adjacent to the n
21
33
[id="bug-fix-rhidp-6448"]
22
34
=== Manually added resolutions override resolutions added by `--suppress-native-package`
23
35
24
-
Previously, manually added resolutions were not overwritten by the package export-dynamic-plugin command. This could lead to incorrect package dependencies in the exported dynamic plugin.
36
+
Earlier, the `export-dynamic-plugin` command did not overwrite manually added resolutions, which could result in incorrect package dependencies in the exported dynamic plugin.
25
37
26
38
With this update, the `package export-dynamic-plugin` overwrites manually added resolutions, ensuring backstage dependencies are hoisted and native dependencies are suppressed from the exported dynamic plugin.
Copy file name to clipboardExpand all lines: modules/release-notes/ref-release-notes-new-features.adoc
+48-1Lines changed: 48 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,48 @@
4
4
5
5
This section highlights new features in {product}{product-version}.
6
6
7
+
[id="feature-rhidp-3597"]
8
+
== OpenTelemetry metrics support added to the Keycloak backend plugin
9
+
10
+
With this update, the Keycloak backend plugin supports OpenTelemetry metrics, which monitors fetch operations and diagnoses potential issues.
11
+
12
+
The available counters include the following:
13
+
14
+
`backend_keycloak_fetch_task_failure_count_total`: Counts fetch task failures where no data was returned due to an error.
15
+
16
+
`backend_keycloak_fetch_data_batch_failure_count_total`: Counts partial data batch failures. Even if some batches fail, the plugin continues fetching others.
17
+
18
+
These counters include the `taskInstanceId` label, which uniquely identifies each scheduled fetch task, and allows you to trace failures back to individual task executions.
You can export metrics using any OpenTelemetry-compatible backend, such as **Prometheus**.
27
+
28
+
29
+
[id="enhancement-rhidp-5987"]
30
+
== Updated RBAC and Bulk Import plugins
31
+
32
+
{product} {product-version} introduces an enhancement to the RBAC and Bulk Import plugins, enabling users to utilize Backstage's new Auditor service. The key features include:
33
+
34
+
* Audit log format update:
35
+
36
+
The audit log format has been updated to align with the new Auditor service conventions. Audit fields and event identifiers have been updated. Filtering queries based on the old format may no longer function as expected.
37
+
38
+
* Backend Plugin API integration:
39
+
40
+
The audit log is now backed by the `@backstage/backend-plugin-api` package.
41
+
42
+
* Audit events Grouping:
43
+
44
+
The Bulk Import backend plugin emits audit events for various operations, with the events are grouped logically by `eventId`.
45
+
46
+
47
+
48
+
7
49
[id="feature-rhidp-6253"]
8
50
== {product-short} community plugins updated to Backstage 1.36
9
51
@@ -12,10 +54,15 @@ The {product-short} community plugins have been updated to Backstage version 1.3
12
54
[id="feature-rhidp-6269"]
13
55
== Added a new RBAC conditional rule `IS_OWNER` to RBAC plugin
14
56
15
-
{product} has introduced a new RBAC conditional rule `IS_OWNER` that allows administrators to grant limited access to the RBAC plugin. This enhancement allows administrators to assign ownership to roles and control their team's access. Therefore, users can assign ownership to roles, which can be used to conditionally filter roles, permission policies, and conditional policies.
57
+
{product} introduces a new RBAC conditional rule, `IS_OWNER`, that allows administrators to assign ownership to roles and control access to the RBAC plugin. This enhancement enables more granular access control by allowing ownership-based filtering of roles, permission policies, and conditional policies.
16
58
17
59
This enhancement removes the resource type from the `policy.entity.create` permission, preventing conditional rules from being applied to the permission. You can update all permission policies that utilize the resource type `policy-entity` with the action `create` (for example `role:default/some_role, policy-entity, create, allow` to `role:default/some_role, policy.entity.create, create, allow`) to prevent degradation in the future.
18
60
19
61
62
+
[id="enhancement-rhidp-6882"]
63
+
== Default OIDC sign-in resolver updated
64
+
65
+
With this update, the default resolver for OIDC sign-in is set to `oidcSubClaimMatchingKeycloakUserId` to enhance security. This resolver is now also available as a configurable option under the sign-in resolver settings.
0 commit comments