Description of problem:

In RHDH 1.6, creating the secret dynamic-plugins-npmrc in the backstage namespace will cause the backstage deployment to mount the secret and use it to override the dynamic plugin .npmrc to use a non-default npm registry, such as https://npm.stage.registry.redhat.com

I have tried to do this in 1.7 and I see that it does not get mounted. This is causing my backstage dynamic plugins to fail to load as they are in stage, not prod.

Prerequisites (if any, like setup, operators/versions):

RHDH operator 1.7 with alternate registry set in dynamic-plugins-npmrc

Steps to Reproduce

• deploy rhdh 1.7 operator with backstage
• create a dynamic-plugins-npmrc secret with a different npm registry
• Try to deploy plugins from the other registry

Actual results:

Plugins will not be found as the npmrc file is no mounted

Expected results:

npmrc is mounted and plugins are found

Reproducibility (Always/Intermittent/Only Once):

100%

Build Details:

RHDH 1.7 operator pre-release

Additional info (Such as Logs, Screenshots, etc):

More logs are attached

RHDH 1.6 backstage deployment has this mounted:

        - mountPath: /opt/app-root/src/.npmrc.dynamic-plugins
          name: dynamic-plugins-npmrc
          readOnly: true
          subPath: .npmrc
 

But RHDH 1.7 backstage deployment does not. 

Both have dynamic-plugins-npmrc secret created in the backstage namespace.