User interface for Red Hat Managed Services (Kafka, Service Registry etc.) that is available as part of the https://console.redhat.com
Application Services UI is based on the https://github.com/RedHatInsights/insights-frontend-starter-app.git which is React.js starter app for Red Hat Insights products that includes Patternfly 4 and shared cloud.redhat.com services
- Managed Kafka UI (https://github.com/bf2fc6cc711aee1a0c2a/kas-ui)
- Kafka instance UI (https://github.com/bf2fc6cc711aee1a0c2a/kafka-ui)
- Service Registry UI (https://github.com/bf2fc6cc711aee1a0c2a/srs-ui)
- API Designer UI (https://github.com/bf2fc6cc711aee1a0c2a/ads-ui)
- Guides (https://github.com/redhat-developer/app-services-guides)
Project can be run in two modes:
- Using remote federated components from console.redhat.com (only for Red Hat Internal usage)
- Running federated modules locally (dev)
Run:
npm install
npm run start:dev
Go to https://prod.foo.redhat.com:1337/beta/application-services/streams/kafkas
First we need to download all external repositories by running a script.
./hack/checkout-repos.sh
After that we can run any of the federated UI component in ./modules
folder and it will automatically be used by the app-services-ui
Developers running app-services-ui on their local machines can point it to custom backends and authentication providers. To point UI to different backend we need to modify config.json configuration file on your local machine.
For example for configuring UI to run against Kas-installer we can change
1kas.apiBasePath1 value to kafka url returned by kas-installer.
For more information please refer to kas-installer
- Edit
webpack.dev.js
and add the following toproxyConfig
:
routes: {
'/config': { host: 'http://127.0.0.1:8889' },
'/beta/config': { host: 'http://127.0.0.1:8889' }
},
- Clone https://github.com/RedHatInsights/cloud-services-config and follow the instructions there to make your changes
- run npx http-server -p 8889 in cloud-services-config to try the changes out