@redhat-cloud-services/frontend-components-inventory-vulnerabilities

Vulnerability UI

First time setup

Quick start

1. Make sure you have Node.js and npm installed
2. Run script to patch your /etc/hosts
3. Make sure you are using Red Hat proxy

Comprehensive documentation

There is a comprehensive quick start guide in the Storybook Documentation to setting up an Insights environment.

Running locally

1. Install dependencies with npm install
2. Run development server with npm run start:proxy:beta
3. Local version of the app will be available at https://stage.foo.redhat.com:1337/beta/insights/vulnerability/

Testing

Jest is used as the testing framework

• npm run test - run all tests
• npm run test -- testName - run tests for all components matching testName
• npm run lint - run linter
• npm run test:update - run all tests and update snapshots
• npm run test:watch - run tests in watch mode

Deploying

Any push to the following branches will trigger a build in vulnerability-ui-build repository which will deploy to corresponding environment.

Push to branch in this repo	Updated branch in build repo	Environment	Available at
master	stage-beta	stage beta	https://console.stage.redhat.com/beta
stage-stable	stage-stable	stage stable	https://console.stage.redhat.com
prod-beta	prod-beta	production beta	https://console.redhat.com/beta
prod-stable	prod-stable	production stable	https://console.redhat.com

Internationalization

Translation keys

Translation keys are saved in messages.js.

Generating translation keys

Each time you add a new translation keys you need to run npm run translations, which will automatically generate JSON files for every language into locales/ folder based on the entries in the messages.js.

Using translated strings

There are two ways to use translated strings:

1. With intl.formatMessage(messages.messageId)
2. With <FormattedMessage {...messages.messageId}/>

Design System

This project uses Patternfly React.

Insights Components

This app imports components from Insights Front-end Components library. ESI tags are used to import Insights Chrome which takes care of the header, sidebar, and footer.

Versioning

This project uses Semantic Versioning. Release process is automated by using Semantic Release.