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
chore(release notes): regenerate missing content from JIRA (#1552)
* chore(release notes): regenerate missing content from JIRA
Signed-off-by: Nick Boldt <[email protected]>
* remove item for orch 1.7.1; add KI for orch 1.8.2 (which will be fixed in 1.9)
Signed-off-by: Nick Boldt <[email protected]>
---------
Signed-off-by: Nick Boldt <[email protected]>
== {ls-brand-name} now uses Lightspeed Core (LCORE)
37
37
38
-
With this update, RHDH Local includes comprehensive technical TechDocs covering everything you need to know about it.
39
-
Once running, access the built-in documentation directly in the application for detailed guides.
38
+
The {ls-short} plugin has completed its migration from the Road-Core Service to Lightspeed Core (LCORE). This architectural change provides enhanced stability and prepares the plugin for future feature development during the Developer Preview.
== Enhanced customozation and collaboration with pre-loaded templates in RHDH Local
63
+
== Enhanced customization and collaboration with pre-loaded templates in RHDH Local
65
64
66
65
With this update, RHDH Local integrates pre-loaded essential templates, enabling users to create their own custom plugins and add TechDocs or software components to existing projects within {product}. This enhancement demonstrates {product-short} extensibility, empowers users to extend the platform, and enhances the overall user experience by promoting collaboration and customization.
=== Fixed SCM integration failures for self-hosted enterprise SCM providers
64
65
65
-
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.
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.
66
67
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.
Before this update, the latest Orchestrator feature set was unavailable because the release included the outdated Orchestrator plugin version `1.6`. This issue is resolved in {product-very-short} `1.7.1`. The Orchestrator plugin is now updated to version `1.7.1`, ensuring that users have access to the latest features and functionality.
Copy file name to clipboardExpand all lines: modules/release-notes/ref-release-notes-known-issues.adoc
+34Lines changed: 34 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,40 @@
5
5
6
6
This section lists known issues in {product} {product-version}.
7
7
8
+
[id="known-issue-rhdhbugs-2240"]
9
+
== Existing Operator users with Orchestator 1.7 require a manual update in their dynamic-plugins ConfigMap
10
+
11
+
If you have an existing Operator-backed instance of {product-short} with the Orchestrator, you must update your dynamic-plugins ConfigMap to set the version of the Orchestrator plugins to 1.8.2 once the {product-short} Operator is upgraded to 1.8.
12
+
Otherwise, the {product-short} instance will not be upgraded at all.
13
+
14
+
.Example of a dynamic-plugins ConfigMap enabling the Orchestrator plugins in 1.8 for Operator-backed instances
0 commit comments