This documentation is for a release that is no longer maintained
See documentation for the latest supported version.Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 5. Known issues
This section lists known issues with Red Hat Developer Hub 1.2:
- Deprecation warning: The backend.auth.keys config has been replaced by backend.auth.externalAccess
-
Due to changes to the backend service-to-service authentication, you will see a deprecation warning if you have set up your deployment to use the
backend.auth.keysfield configured inupstream.backstage.appConfigThis warning is harmless for now and no action is needed. - IP addresses may appear in application logs
If you deploy Developer Hub without a proxy, there is the potential for IP addresses to appear in the audit logs. If your organization’s security policies restrict you from retaining IP addresses, you can take one or both of the following actions:
- Delete the IP addresses after they are collected.
- Prevent collection of IP addresses by configuring a reverse proxy in front of Developer Hub.
- Missing items in catalog or software templates after upgrade to Developer Hub 1.2
After upgrading to Developer Hub 1.2, user policies are not automatically migrated or updated, resulting in items not appearing in the catalog or software templates.
To resolve this issue, after upgrading to version 1.2, users need to add the necessary policies in the Developer Hub RBAC system page.
- Rollbacks are not supported
- If you deploy Developer Hub using either Helm or the Operator, rollbacks to earlier versions are not supported. Performing regular backups of your Developer Hub PostgreSQL database helps you to restore the application to a recent state in case of issues. In future versions of Developer Hub, we plan to provide guidance on how to perform rollbacks from existing backups.