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
=== Fixed SCM integration failures for self-hosted enterprise SCM providers
65
-
66
-
Before this update, the SCM integration failed due to lack of identification of the configured authentication provider for self-hosted enterprise SCM hosts. As a consequence, users experienced failed actions with self-hosted enterprise SCM providers due to missing authentication.
67
-
68
-
With this release, the SCM integration now correctly uses the configured authentication provider for corresponding enterprise host. As a result, end users can now successfully perform actions requiring enterprise SCM access.
=== Fixed incorrect version detection for local plugin updates
78
-
79
-
Before this update, local plugins within the image were incorrectly detected for updates due to version misidentification. This led to users being unable to update local plugins from wrappers, resulting in outdated functionality. With this release, local plugin updates are now automatically detected, eliminating the need for manual adjustments and ensuring seamless plugin version updates for end users.
== MUI v5 components might render with broken styles in non-bundled plugins
42
+
[id="known-issue-rhdhbugs-2227"]
43
+
== Deployment update error with dynamic plugin configuration
44
44
45
-
Plugins that are not bundled with {product}, meaning not part of the {product} wrappers, might experience styling issues or broken visuals when using Material UI v5 components.
45
+
Updating the deployment configuration using the `values.yaml` to include specific dynamic plugin configurations might cause an error during the deployment process.
46
46
47
-
. Workaround
48
-
* Add the following code to the plugin’s entry file, such as `workspaces/<pluginId>/plugins/<pluginId>/src/index.ts`:
49
-
+
50
-
[source,javascript]
51
-
----
52
-
import { unstable_ClassNameGenerator as ClassNameGenerator } from '@mui/material/className';
47
+
When configuring the `dynamicRoutes` for the `red-hat-developer-hub.backstage-plugin-dynamic-home-page` plugin, the use of the placeholder {{firstName}} in a configuration property, for example title, can result in the following fatal deployment error:
== Starting time is not displayed correctly in Results pane when workflows are started
62
72
73
+
There is an known issue with the displayed starting time in the Orchestrator 1.8.2 plugins when starting a workflow. When a workflow starts executing, the starting time is not displayed correctly in the Results window of the workflow instance. It remains this way until the workflow changes state. This will be fixed in a future release.
== Clicking on the dedicated {product-very-short} local guide link in the UI sidebar also highlights the Catalog item
69
80
70
-
To resolve Out-Of-Memory errors in the {product} Operator, adjust memory settings manually:
81
+
In this update, the {product-very-short} Local default configuration includes built-in TechDocs. However, when selecting the new "{product-very-short} Local Guide" link in the {product-very-short} Local UI sidebar, the `Catalog` link is also highlighted.
. In the editor, set the memory request to 1 GiB and the limit to 2 GiB:
79
-
+
80
-
[source,yaml]
81
-
----
82
-
spec:
83
-
containers:
84
-
- name: rhdh-operator
85
-
resources:
86
-
requests:
87
-
memory: "1G"
88
-
limits:
89
-
memory: "2G"
90
-
----
87
+
[id="known-issue-rhdhbugs-2126"]
88
+
== Handle installation disabled scenario in the installed packages page
91
89
92
-
. Reapply this change whenever the Operator is actively reconciled. The pod should become healthy, using about 1.07 GiB of memory.
90
+
When installation is disabled, the actions on the Installed Packages page are still shown. Similarly, if the YAML file is misconfigured, the actions appear, but the API call fails with an error. This doesn't break the UI, the API failure is handled gracefully, and the correct reason for the failure is displayed in the UI.
== Starting time is not displayed correctly in Results pane when workflows are started
100
-
There is an known issue with the displayed starting time in the Orchestrator 1.8.2 plugins when starting a workflow. When a workflow starts executing, the starting time is not displayed correctly in the Results window of the workflow instance. It remains this way until the workflow changes state. This will be fixed in a future release.
103
+
[id="known-issue-rhdhbugs-2059"]
104
+
== Error message when manually accessing accessing plugins without associated entity YAML
105
+
106
+
This error occurs when a user tries to access a package or plugin that does not have an associated entity YAML. Users will not encounter this error under normal usage; it only appears if they manually modify the plugin or package name in the URL. This ticket will handle this scenario more gracefully by indicating why access to a particular plugin is not allowed.
== MUI v5 components might render with broken styles in non-bundled plugins
171
+
172
+
Plugins that are not bundled with {product}, meaning not part of the {product} wrappers, might experience styling issues or broken visuals when using Material UI v5 components.
173
+
174
+
. Workaround
175
+
* Add the following code to the plugin’s entry file, such as `workspaces/<pluginId>/plugins/<pluginId>/src/index.ts`:
176
+
+
177
+
[source,javascript]
178
+
----
179
+
import { unstable_ClassNameGenerator as ClassNameGenerator } from '@mui/material/className';
0 commit comments