Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

Chapter 5. Enable and configure the Nexus Repository Manager plugin

Use the Nexus Repository Manager plugin to view build artifacts in your Developer Hub application. You can find this community-sourced plugin in the Community plugins migration table.

5.1. Enable the Nexus Repository Manager plugin
Copiar enlace

To enable the Nexus Repository Manager plugin, set the disabled property to false.

Procedure

  • Set the value to false as follows: 

    global:
  dynamic:
    includes:
      - dynamic-plugins.default.yaml
    plugins:
      - package: oci://ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-nexus-repository-manager:<tag>
        disabled: false

    The <tag> variable is your RHDH application's version of Backstage and the plugin version, in the format: bs_<backstage-version>__<plugin-version> (note the double underscore delimiter).

  • To find the correct image tag for <tag>:

    1. Look in the RHDH release notes preface for your Backstage version.
    2. Locate the plugin version for paths starting with oci://ghcr.io within one of the tables in the Dynamic Plugins Reference guide.

For example, because RHDH 1.9 is based on Backstage 1.45.3, the tag will have the format bs_1.45.3__<plugin-version>.

Tip

To ensure environment stability, use a SHA256 digest instead of a version tag. See Determining SHA256 Digests.

5.2. Configure the Nexus Repository Manager plugin
Copiar enlace

Configure the Nexus Repository Manager plugin to display artifact information from your Nexus Repository Manager instance.

Procedure

  1. Set the proxy to the required Nexus Repository Manager server in the app-config.yaml file as follows: 

    proxy:
    '/nexus-repository-manager':
    target: 'https://<NEXUS_REPOSITORY_MANAGER_URL>'
    headers:
        X-Requested-With: 'XMLHttpRequest'
        # Uncomment the following line to access a private Nexus Repository Manager using a token
        # Authorization: 'Bearer <YOUR TOKEN>'
    changeOrigin: true
    # Change to "false" in case of using self hosted Nexus Repository Manager instance with a self-signed certificate
    secure: true

  2. Optional: Change the base URL of Nexus Repository Manager proxy as follows: 

    nexusRepositoryManager:
    # default path is `/nexus-repository-manager`
    proxyPath: /custom-path

  3. Optional: Enable the following experimental annotations: 

    nexusRepositoryManager:
    experimentalAnnotations: true

  4. Annotate your entity using the following annotations: 

    metadata:
    annotations:
    # insert the chosen annotations here
    # example
    nexus-repository-manager/docker.image-name: `<ORGANIZATION>/<REPOSITORY>`,
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Legal Notice

Theme

© 2026 Red HatVolver arriba