Fixed issues
This section lists issues fixed in Red Hat Developer Hub 2.1.
Fixed issues in 2.1.0
The rhdh-cli plugin package command uses npm pack for staging
Before this update, the rhdh-cli plugin package command performed a recursive copy of the contents of the dist-dynamic folder that is created by the rhdh-cli plugin export command. With this update, the command uses npm pack and extracts the result into its staging directory before it copies the exported plugin to its final destination or starts the container image build.
Additional resources
Improved accessibility of the Light theme
Before this update, several UI elements did not meet Web Content Accessibility Guidelines (WCAG) 2.1 AA standards when the Red Hat Developer Hub Light theme was applied. The problems included buttons and toggle switches without accessible names, invalid ARIA attributes on tabs, list items with incorrect markup, interactive controls nested inside other controls in sortable table headers, and some text with insufficient color contrast. As a result, screen readers and other assistive technologies could not correctly read or use some parts of the interface. With this update, these problems are fixed in the Theme plugin. The Light theme now works better with assistive technologies and meets the required contrast ratios.
Additional resources
The OwnedEntityPicker field no longer fails with an HTTP 431 error
Before this update, the OwnedEntityPicker field in software templates could fail with an HTTP 431 Request Header Fields Too Large error for users who belong to many groups with long names when multiple catalogFilter entries were configured. With this release, the picker correctly displays the entities that are owned by the user or their groups.
Additional resources
The Orchestrator database creation Job is renamed and fails correctly on errors
The Orchestrator database creation Job is renamed from <release>-create-sonataflow-database to <release>-create-sf-db-<version>. When you upgrade, the old Job remains on the cluster and can be safely deleted manually.
Before this update, the Job could silently succeed even when a database error occurred. With this release, the Job fails correctly on database errors and retries according to the backoffLimit setting (default: 2).
The following settings are now configurable in the values.yaml file:
-
backoffLimit -
activeDeadlineSeconds -
ttlSecondsAfterFinished
The ttlSecondsAfterFinished setting is disabled by default to prevent Argo CD reconciliation loops. Set it explicitly if you want automatic cleanup.
Additional resources
Scaffolder annotator action descriptions and examples are improved
Before this update, the in-app self-documentation for the catalog:annotate, catalog:scaffolded-from, catalog:template:version, and catalog:timestamping actions in the Installed Actions catalog contained confusing descriptions and lacked code examples. With this update, the action descriptions are clarified to accurately state what each action does, and ready-to-use examples are added.
Additional resources
Catalog search visibility matches catalog browsing for HAS_LABEL and HAS_ANNOTATION policies
Before this update, when catalog.entity.read was authorized with a conditional policy that used the built-in HAS_LABEL or HAS_ANNOTATION rule, entities could appear in the Software Catalog but be missing from catalog-backed search results, including TechDocs search. This happened when the label or annotation key in the entity YAML did not use the same casing as the name in the policy, for example, isPublic in the policy compared with ispublic in the YAML. The catalog list and query path normalized casing in its database filter, but the search authorization path evaluated the entity JSON with case-sensitive matching.
With this update, the HAS_LABEL and HAS_ANNOTATION permission rules evaluate label and annotation keys and values case-insensitively, so catalog browsing and search visibility stay consistent for the same entity and policy.
Additional resources
Repository publishing actions no longer fail behind DPI proxies
Before this update, the repository publishing actions (publish:github and github:repo:push) failed with an ECONNRESET error in enterprise environments that use Deep Packet Inspection (DPI) proxies. With this release, a fallback mechanism routes pushes through the GitHub GraphQL API over standard HTTPS JSON when binary Git smart protocol packets are rejected.
Additional resources
The AppBar no longer displays a box shadow
Before this update, the AppBar component displayed a box shadow that was inconsistent with the Red Hat Developer Hub design. With this release, the box shadow is removed.
Additional resources
Hidden custom widgets no longer leave blank spaces in Orchestrator workflow forms
Before this update, custom widgets in an Orchestrator workflow form that were marked with "ui:hidden": true, such as ActiveTextInput, ActiveMultiSelect, and SchemaUpdater, still rendered their container element, which produced large vertical blank spaces between visible fields. With this release, these hidden custom widgets are fully collapsed and no longer leave blank spaces.
Additional resources
Setting an empty flavours array now disables all default flavours
Before this update, setting spec.flavours: [] (an empty array) in a Backstage custom resource (CR) did not disable the default flavours, and flavours with enabledByDefault: true were still loaded. With this update, setting spec.flavours: [] disables all default flavours, as documented. To use the default flavours, omit the spec.flavours field. The YAML syntax is unchanged.
Additional resources
GitHub SAML SSO token expiration no longer causes 403 error
Before this update, when a GitHUB SAML SSO session expired, users would experience a 403 error despite having valid tokens.
With this update, you can add a GitHub SAML SSO check step to your workflows. If the check detects a SAML SSO expiration, a re-authentication prompt appears.
Additional resources
Irrelevant wizard steps are hidden
Before this update, wizard steps that did not apply were still shown. With this release, these steps are hidden when they are not relevant.
Additional resources
Filtering workflow runs by status and date works correctly
Before this update, an error occurred when you filtered workflow runs by status and date. With this release, the workflow run list loads as expected when you use those filters.
Additional resources
Scorecard supports service account tokens for Jira Cloud
Before this update, the Scorecard Jira provider supported only the default authentication method. Because Jira Cloud defaults to basic authentication, which is used for standard user tokens, you could not use service account tokens, which require bearer authentication. With this update, you can configure custom authentication types, so that service account tokens are fully supported.
Additional resources
Orchestrator workflow form validation errors clear as you enter a new value
Before this update, field-level and top-level validation errors in an Orchestrator workflow form stayed visible after you entered a new value. With this release, these validation errors clear as you enter a new value.
Additional resources
Orchestrator Loki backend module no longer fails validation and crashes on boot
Before this update, Orchestrator Loki backend module would fail validation and crash on boot if logPipelineFilters in app-config-yaml file contained brace characters { and } (standard LogQL text template syntax). This caused the local configuration validator to intercept the string value and reject the opening brace character.
With this release, correctly formatted LogQL values are accepted by the validator.
Additional resources
Workflow run detail cards no longer overlap in content height mode
Before this update, when the card height mode was set to content, the workflow run detail cards (Inputs and Results) could overlap, which caused overlapping text and broken layouts. With this release, the cards display correctly regardless of content size.
Additional resources
TechDocs page and table of contents scrollbars no longer overlap
Before this update, when you viewed a TechDocs page, the document scrollbar and the table of contents scrollbar overlapped, which made the page difficult to use. With this release, scrolling occurs at the outer page level, and the scrollbar is positioned at the viewport edge so that it no longer conflicts with the table of contents scrollbar.
Additional resources
Dynamic plugin installation no longer delays pod termination
Before this update, when the install-dynamic-plugins init container received a SIGTERM signal during a pod rolling update, eviction, or scale-down, child processes such as skopeo and npm were not terminated. These orphaned processes continued running until Kubernetes sent SIGKILL after the termination grace period, which caused pod shutdowns to take 30 to 139 seconds.
With this release, the init container shell wrapper forwards SIGTERM to the entire process group, so that all child processes are terminated immediately. Pod shutdowns during dynamic plugin installation now complete in less than 5 seconds.
Additional resources
The RBAC interface performs better with large numbers of users and groups
Before this update, the role-based access control (RBAC) interface became slow or unresponsive in environments with large numbers of users and groups. With this release, role page loading and member selection are improved, and the Edit button is no longer blocked while member data loads.
Additional resources
The intelligent assistant button no longer overlaps pagination controls
Before this update, the intelligent assistant (formerly Developer Lightspeed) floating action button (FAB) overlapped the pagination controls, which made the Next button difficult to select. With this update, the floating action button is positioned above the pagination controls so that the Next button remains clickable.
Additional resources
The jira/custom-filter annotation value is validated
Before this update, the value of the jira/custom-filter entity annotation was inserted into the Jira Query Language (JQL) query generated for the jira.openIssues metric without sufficient validation. A malformed or crafted value could therefore change the structure of the query rather than only narrowing which issues were counted, producing an incorrect issue count or a Jira query error.
With this update, the annotation value is checked before the query is built. Parentheses and brackets must be balanced, string literals must be terminated, and a backslash is permitted only inside a string literal. Values that contain control characters, an ORDER BY clause, or a leading wildcard, or that are longer than 1,000 characters, are rejected. An invalid value now fails with an error that names the annotation and the reason, instead of being sent to Jira.
Additional resources
Disabled Scorecard metrics are no longer displayed from the database
Before this update, disabling a metric, either globally in app-config.yaml or at the entity level by using annotations, stopped metric collection, but previously stored database values remained visible on the entity page, the homepage aggregated Scorecard cards, and the Scorecard Entities page. With this release, disabled metrics are hidden as follows:
- Globally disabled metrics: Hidden from the entity page, the homepage, and the Scorecard Entities page.
- Entity-level disabled metrics: Hidden from these surfaces only for the specific entities where they are disabled.
Additional resources
Toggling themes no longer remounts the application tree
Before this update, toggling the theme triggered a full application tree remount, which caused unnecessary re-renders and lost local component state. With this release, toggling the theme no longer remounts the application tree, and local component state is preserved.
Additional resources
The Helm chart selects the correct PostgreSQL password secret key for custom usernames
Before this update, the Red Hat Developer Hub Helm chart always used the postgres-password key, so a custom database username could not authenticate to the bundled PostgreSQL instance and the backend failed to start. With this release, the Helm chart selects the correct PostgreSQL password secret key when postgresql.auth.username is set to a value other than postgres.
Additional resources
Disabled metrics are hidden from Scorecard aggregated cards on the homepage
Before this update, disabling a metric, either globally in app-config.yaml or at the entity level by using annotations, stopped metric collection, but previously stored database values remained visible on the homepage aggregated Scorecard cards and the Scorecard Entities page. With this release, disabled metrics are hidden as follows:
- Globally disabled metrics: Hidden from both the homepage and the Scorecard Entities page.
- Entity-level disabled metrics: Hidden from the aggregated Scorecard cards and the Scorecard Entities page, only for the specific entities where they are disabled.
Additional resources
Plugin builds now use up-to-date Adobe Spectrum, React Aria, and React Stately dependencies
Before this update, the lockfile pinned the Adobe Spectrum, React Aria, and React Stately dependencies to outdated versions, so product builds of the plugins did not include the latest versions of these dependencies. With this release, the lockfile pinning is fixed, and the plugins are built with up-to-date Adobe Spectrum, React Aria, and React Stately dependencies.
Additional resources
Accessibility issues are resolved across GA plugins
Before this update, several Red Hat-owned generally available (GA) frontend plugins in Red Hat Developer Hub contained accessibility issues. With this release, these plugins are reviewed and tested for conformance with Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, and the known accessibility issues are resolved.
Additional resources