Chapter 2. Breaking changes

Before this update, the dynamic-plugins config map name was hardcoded. Therefore, it was not possible to install two Red Hat Developer Hub helm charts in the same namespace.

With this update, the dynamic-plugins config map is named dynamically based on the deployment name similar to how all other components names are generated. When upgrading from a previous chart you might need to manually update that section of your values.yaml file to pull in the correct config map.

By default, it is now required for the user entity to exist in the software catalog to allow sign in. This is required for production ready deployments since identities need to exist and originate from a trusted source (i.e. the Identity Provider) in order for security controls such as RBAC and Audit logging to be effective. To bypass this, enable the dangerouslySignInWithoutUserInCatalog configuration that allows sign in without the user being in the catalog. Enabling this option is dangerous as it might allow unauthorized users to gain access.

Before this update, some Red Hat and Community Technology Preview (TP) plugins and actions were enabled by default:

With this update, all plugins included under the Technology Preview scope of support, whether from Red Hat or the community, are disabled by default.

With this update, three plugins previously under the @janus-idp scope have moved to @backstage-community:

As the scope of the previous plugins has been updated, the dynamic plugin configuration has also changed.