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
Currently, the environment variables for the registry viewer are being set under a mounted envfile /app/apps/registry-viewer/.env.local. It should be set under a mounted envfile /app/.env.production, in addition the environment variables needs to be loaded on deployment in the template spec rather than just loaded from the envfile by Next.js.
Which area this feature is related to?
/kind bug
Which area this bug is related to?
/area registry
What versions of software are you using?
Go project
Operating System and version: RHEL 8.7
Go Pkg Version: 1.17
Node.js project
Operating System and version:
Node.js version: 16
Yarn version: 1.22.19
Project.json:
Bug Summary
Describe the bug:
Currently, the environment variables for the registry viewer are being set under a mounted envfile
/app/apps/registry-viewer/.env.local
. It should be set under a mounted envfile/app/.env.production
, in addition the environment variables needs to be loaded on deployment in the template spec rather than just loaded from the envfile by Next.js.blocks #1006, #1014
To Reproduce:
Deployment using the current OpenShift template specs and registry operator.
Expected behavior
Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable
Additional context
Any workaround?
None.
Suggestion on how to fix the bug
Environment variables need to be set in both the mounted envfile and in the deployment spec.
Target Date: 02-09-2023
The text was updated successfully, but these errors were encountered: