Developer Activity: Update a Component’s Catalog Info

The Argo CD Backstage plugin brings sync status, health status, and update history of your Argo CD Application to your Red Hat Developer Hub’s Component view. However, simply installing the Argo CD plugin doesn’t automatically make the associated deployment information visible when viewing Components in the Software Catalog. An argocd/app-selector annotation must be added to the Component’s YAML definition. This annotation instructs the Argo CD plugin to fetch the information related to the Component from the Argo CD instance you configured.

Please ensure you are logged in as a Developer with dev1 / {common_password} as you were guided to in a previous step.

Update the Catalog Info

Update your Quarkus application’s catalog-info.yaml with the correct annotation:

  1. Visit the dev1/my-quarkus-app/catalog-info.yaml file in GitLab.

  2. Select Edit > Edit single file.

  3. Uncomment the following annotation:

    argocd/app-selector: rht-gitops.com/rhdh-gitops=dev1-my-quarkus-app

  4. You can confirm this annotation is correct by visiting the dev1-my-quarkus-app-dev in the rhdh-gitops instance and clicking the Details button to view the applied labels. Login as admin using {common_password} if prompted.

    Argo CD Details with Labels

  5. Scroll down and enter a commit message feat: Add argocd/app-selector annotation.

  6. Use the Commit changes button to commit the annotation.

Refresh the Entity’s Catalog Info

  1. Return to your instance of Red Hat Developer Hub after committing the change to view the newly created my-quarkus-app Component. Use the Schedule entity refresh button to pull this change from Git to Red Hat Developer Hub for your Quarkus application.

    Entity Refresh Button

  2. Next, refresh your browser. The CD tab should appear, and you can view the Argo CD Application’s information.

    CD Tab in Component

Summary

Congratulations! You updated your Component’s dev1/my-quarkus-app/catalog-info.yaml, and enabled new functionality using a plugin specific annotation.