Goal

Once #83 is complete, review the plugin evaluation document and map out the next steps.

Acceptance Criteria

Update #111 with goals discussed in the Spike review

🔌 Plugin: Ingest users and groups from OCP

🔖 Summary

Create a new plugin to ingest users and groups from OCP

🌐 Project website (if applicable)

No response

✌️ Context

@sabre1041 is looking into this

👀 Have you spent some time to check if this plugin request has been raised before?

I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

I have read the Contributing Guidelines

Are you willing to submit PR?

None

Spike review: GitHub Issues

Now that the spike on GitHub Issues is complete, we need to review the plugin evaluation doc and map out next steps.

Goal

Review the upstream Janus keycloak plugin.
(do we need a template for this?)

Why is this needed?

Review features and functionality of this plugin.

Acceptance Criteria

Identify and add GH stories needed before this epic is considered "complete" for Milestone 01 (tag with appropriate milestone & include in #54
Identify and add GH stories, considered as enhancements which can be accomplished before Milestone 01

🔌 UI Plugin: Application Topology

Goal

The goal of this epic is to develop a new Backstage UI plugin in the Janus repo. This UI plugin should provide similar functionality from the Application Topology view in the OpenShift Developer Perspective of the console. The current Application Topology supports a large set of features.

This plugin will provide an initial set of features, which will continue to be enhanced, based on the success metrics of the initial version of this plugin, including customer feedback.

The plugin will initially be view only
The plugin will initially only provide the graph view
The plugin will visualize information/status in real time
The visual representations of objects from a shape and hierarchy standpoint will be consistent with what is shown in OpenShift today.
Nodes will display a pod ring so that users are easily able to see the status of the pods associated with the workloads
Provide a route decorator
Side panel showing details of the kubernetes objects
Resource tab in the side panel showing the associated resources
Implement the GH and DevSpaces decorator (stretch)

What problem does this solve? Please describe.

Users want to be able to see the status of the workloads associated with a service in your catalog which is deployed to any kubernetes cluster.
Users want one click access to pod logs
Users want one click access to run their application which is running on kubernetes

Features
Need to look into this further

Provide a Topology tab on the entity page which provides the graph view of the application topology ( list view will. come later)
OR
Provide a Topology Card on that visualizes the directly related workloads of the current entity.
Provide a Topology Page which can be access from the Topology Card, and is able to view the workloads associated with the current entity as well as workloads associated with their relations.

Use cases
Coming after spike review

Acceptance criteria
Coming after spike review

Issues in Epic

Stakeholder sign-off

QE
Doc

Reference screenshots from OpenShift Application Topology

Topology graph view

Topology graph view with side panel showing kubernetes details

Topology graph view with side panel showing associated resources

🔌 Plugin: Environments

Goals

This epic aims to develop a new Backstage UI plugin in the Janus repo. We want to look into the functionality from the Application Environments view in the OpenShift Developer Perspective of the console, when OpenShift GitOps is installed. As part of this epic, we need to evaluate the features which could be brought in as a plugin, as well as if we need OpenShift GitOps installed, or if Argo is enough. The following features should be evaluated to see if they can be included:

App Env Details page including a high level overview of the status of the app as deployed in each env

Reference screenshots from OpenShift Console / OpenShift GitOps plugin

Lists all applications which are "managed by GitOps"

Provides a high level overview of the status of the application as it's deployed across each "environment"

I

[Dark mode] on the details page and also what happens when there are no commit details for an app

App Topology - Visualize resources of the Deployment kind as readonly

@invincibleJai please update this with initial story for #58

Description
As a developer, I want to visualize resources of the Deployment kind with pods ring demonstrating pod status and decorators for the route in a sample plugin for topology as Read-only. The visualization should be the same as in ODC as part of this work mock the data for the required resources and create the required data model.

Acceptance Criteria

Visualize resource of kind deployment and deployment config in Topology, show associated pod rings along with pod status
Workload resources like Deployments and Pods will be shown in a visual group based on the below label
```
'app.kubernetes.io/part-of': <GROUP_NAME>
```

Workload resources like Deployment or Pod will be shown with a visual connector based on the below annotations

'app.openshift.io/connects-to': '[{"apiVersion": <RESOURCE_APIVERSION>,"kind": <RESOURCE_KIND>,"name": <RESOURCE_NAME>}]'

Push the code to GitHub and any changes need to be documented as required. (Needs to check on with GitHub repo)

Additional Details:

For labels and annotations check https://github.com/redhat-developer/app-labels/blob/master/labels-annotation-for-openshift.adoc

🔌 Plugin: Improve upstream GitHub UI Plugin

Goal

Improve upstream GitHub UI Plugin

What problem does this solve? Please describe.

Application developers want to be able to view GitHub issues associated with their entity.

Use cases

As an application developer using the Backstage portal, I should be able to view GitHub issues for my entity in Backstage.

Acceptance criteria

Evaluate the plugin, using this BS Plugin Evaluation Templates
Review above evaluation and determine next steps
Identify any upstream issues that need to be addressed and fix them

Issues in Epic

#92
#366

🔌 Plugin: Web Terminal

Goal

The goal of this epic is to develop a new Backstage UI plugin in the Janus repo. This UI plugin should provide similar functionality from the OpenShift Web Terminal which is available in the OpenShift Console.

This plugin will provide an initial set of features, which will continue to be enhanced, based on the success metrics of the initial version of this plugin, including customer feedback.

What problem does this solve? Please describe.
-- tbd --

Use cases
As a backstage user, I want easy access to a web terminal running on a cluster in context

Acceptance criteria
-- tbd --

Additional context

Web Terminal Operator: https://github.com/redhat-developer/web-terminal-operator

Screenshots of

OpenShift web terminal for reference

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

Detected dependencies

Note

Detected dependencies section has been truncated

Branch main

dockerfile

packages/backend/Dockerfile

node 19-bullseye-slim@sha256:f58f1fcf5c9ff9e3752993edb4ed6dbd35697124c85a43f3b97aa054500b0534

github-actions

.github/actions/build/action.yaml

actions/setup-node v4@60edb5dd545a775178f52524783378180af0d1f8

dtinth/setup-github-actions-caching-for-turbo v1@a0e976d970c2a94366a26984efcef3030e2c0115

.github/actions/test/action.yaml

actions/setup-node v4@60edb5dd545a775178f52524783378180af0d1f8

dtinth/setup-github-actions-caching-for-turbo v1@a0e976d970c2a94366a26984efcef3030e2c0115

.github/workflows/on-new-issue.yaml

janus-idp/.github main

.github/workflows/pr-playwright.yaml

actions/checkout v4@0ad4b8fadaa221de15dcec353f45205ec38ea70b

actions/setup-node v4@60edb5dd545a775178f52524783378180af0d1f8

actions/checkout v4@0ad4b8fadaa221de15dcec353f45205ec38ea70b

actions/setup-node v4@60edb5dd545a775178f52524783378180af0d1f8

actions/upload-artifact v4@65462800fd760344b1a7b4382951275a0abb4808

.github/workflows/pr-semantic.yaml

amannn/action-semantic-pull-request v5@e9fabac35e210fea40ca5b14c0da95a099eff26f

marocchino/sticky-pull-request-comment v2@efaaab3fd41a9c3de579aba759d2552635e590fd

marocchino/sticky-pull-request-comment v2@efaaab3fd41a9c3de579aba759d2552635e590fd

.github/workflows/pr-website.yaml

actions/checkout v4@0ad4b8fadaa221de15dcec353f45205ec38ea70b

pnpm/action-setup v3

actions/setup-node v4@60edb5dd545a775178f52524783378180af0d1f8

.github/workflows/pr.yaml

actions/checkout v4@0ad4b8fadaa221de15dcec353f45205ec38ea70b

actions/checkout v4@0ad4b8fadaa221de15dcec353f45205ec38ea70b

.github/workflows/publish-backend-plugin-manager.yaml

actions/checkout v4@0ad4b8fadaa221de15dcec353f45205ec38ea70b

actions/checkout v4@0ad4b8fadaa221de15dcec353f45205ec38ea70b

actions/setup-node v4@60edb5dd545a775178f52524783378180af0d1f8

.github/workflows/push-website.yaml

actions/checkout v4@0ad4b8fadaa221de15dcec353f45205ec38ea70b

pnpm/action-setup v3

actions/setup-node v4@60edb5dd545a775178f52524783378180af0d1f8

peter-evans/repository-dispatch v2@bf47d102fdb849e755b0b0023ea3e81a44b6f570

.github/workflows/push.yaml

actions/checkout v4@0ad4b8fadaa221de15dcec353f45205ec38ea70b

actions/create-github-app-token v1.9.3@7bfa3a4717ef143a604ee0a99d859b8886a96d00

actions/checkout v4@0ad4b8fadaa221de15dcec353f45205ec38ea70b

actions/setup-node v4@60edb5dd545a775178f52524783378180af0d1f8

npm

package.json

@ianvs/prettier-plugin-sort-imports 4.1.1

@semantic-release/changelog 6.0.3

@semantic-release/exec 6.0.3

@semantic-release/git 10.0.1

@semantic-release/github 9.2.6

@semrel-extra/npm 1.2.2

@spotify/prettier-config 15.0.0

conventional-changelog-conventionalcommits 6.1.0

eslint-plugin-jest 27.4.2

husky 8.0.3

lint-staged 15.0.1

multi-semantic-release 3.0.2

prettier 3.0.3

turbo 1.10.15

typescript 5.3.3

node 18 || 20

@types/react ^18

@types/react-dom ^18

vscode-languageserver-types 3.17.1

@typescript-eslint/typescript-estree ^7.3.1

packages/app/package.json

@backstage-community/plugin-github-actions ^0.6.16

@backstage-community/plugin-tech-radar ^0.7.4

@emotion/react ^11.11.4

@mui/icons-material ^5.15.16

@mui/material ^5.15.16

@mui/styles ^5.15.16

@redhat-developer/red-hat-developer-hub-theme ^0.0.40

react ^18.0.0

react-dom ^18.0.0

react-router ^6.23.0

react-router-dom ^6.23.0

tss-react ^4.9.10

@testing-library/dom 9.0.0

@testing-library/jest-dom 6.0.0

@testing-library/react 14.0.0

@testing-library/user-event 14.0.0

@types/node 18.19.31

@types/react 18.2.79

@types/react-dom 18.2.25

packages/backend/package.json

packages/cli/package.json

@manypkg/get-packages ^1.1.3

@openshift/dynamic-plugin-sdk-webpack ^3.0.0

@pmmmwh/react-refresh-webpack-plugin ^0.5.7

@rollup/plugin-commonjs ^25.0.4

@rollup/plugin-json ^6.0.0

@rollup/plugin-node-resolve ^15.2.1

@rollup/plugin-yaml ^4.0.0

@svgr/rollup ^8.1.0

@svgr/webpack ^6.5.1

@yarnpkg/lockfile ^1.1.0

@yarnpkg/parsers ^3.0.0-rc.4

bfj ^8.0.0

chalk ^4.0.0

chokidar ^3.3.1

commander ^9.1.0

css-loader ^6.5.1

esbuild ^0.19.0

esbuild-loader ^2.18.0

eslint ^8.49.0

eslint-config-prettier ^8.10.0

eslint-webpack-plugin ^3.2.0

express ^4.18.2

fork-ts-checker-webpack-plugin ^7.0.0-alpha.8

fs-extra ^10.1.0

handlebars ^4.7.7

html-webpack-plugin ^5.3.1

inquirer ^8.2.0

lodash ^4.17.21

mini-css-extract-plugin ^2.4.2

node-libs-browser ^2.2.1

npm-packlist ^5.0.0

ora ^5.3.0

postcss ^8.2.13

process ^0.11.10

react-dev-utils ^12.0.0-next.60

react-refresh ^0.14.0

recursive-readdir ^2.2.2

rollup ^2.78.0

rollup-plugin-dts ^4.0.1

rollup-plugin-esbuild ^4.7.2

rollup-plugin-postcss ^4.0.0

rollup-pluginutils ^2.8.2

semver ^7.5.4

style-loader ^3.3.1

swc-loader ^0.2.3

typescript-json-schema ^0.62.0

webpack ^5.89.0

webpack-dev-server ^4.15.1

yml-loader ^2.1.0

yn ^4.0.0

is-native-module ^1.1.3

@types/express 4.17.20

@types/fs-extra 9.0.1

@types/inquirer 8.1.3

@types/mock-fs 4.13.4

@types/node 18.18.5

@types/npm-packlist 3.0.0

@types/recursive-readdir 2.2.0

@types/rollup-plugin-postcss 3.1.4

@types/yarnpkg__lockfile 1.1.4

mock-fs 5.2.0

msw 1.3.2

nodemon 3.0.1

ts-node 10.0.0

type-fest 4.3.1

@microsoft/api-extractor ^7.21.2

packages/storybook/package.json

@material-ui/core ^4.12.4

@storybook/addon-controls ^7.5.3

@storybook/addon-essentials ^7.5.3

@storybook/addon-interactions ^7.5.3

@storybook/addon-links ^7.5.3

@storybook/blocks ^7.5.3

@storybook/react ^7.5.3

react ^18.2.0

react-dom ^18.2.0

storybook-dark-mode ^3.0.1

@storybook/react-webpack5 7.5.3

@storybook/testing-library 0.2.2

@testing-library/jest-dom 6.4.2

@types/react 18.2.48

@types/react-dom 18.2.18

@swc/core 1.3.96

eslint-plugin-storybook 0.8.0

prop-types 15.8.1

swc-loader 0.2.3

plugins/3scale-backend/package.json

winston ^3.11.0

@types/supertest 2.0.16

msw 1.3.2

supertest 6.3.3

plugins/aap-backend/package.json

winston ^3.11.0

@types/supertest 2.0.16

msw 1.3.2

supertest 6.3.3

plugins/acr/package.json

@material-ui/core ^4.9.13

@material-ui/icons ^4.11.3

@material-ui/lab ^4.0.0-alpha.45

react-use ^17.4.0

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/react-hooks 8.0.1

@testing-library/user-event 14.5.1

@types/node 18.18.5

cross-fetch 4.0.0

msw 1.3.2

react ^16.13.1 || ^17.0.0 || ^18.0.0

plugins/analytics-module-matomo/package.json

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/user-event 14.5.1

@types/node 18.18.5

cross-fetch 4.0.0

msw 1.3.2

react ^16.13.1 || ^17.0.0 || ^18.0.0

plugins/analytics-provider-segment/package.json

@material-ui/core ^4.9.13

@material-ui/icons ^4.11.3

@material-ui/lab 4.0.0-alpha.61

@segment/analytics-next ^1.58.0

prop-types ^15.8.1

react-use ^17.4.0

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/dom 9.3.3

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/user-event 14.5.1

@types/node 18.18.5

@types/react 18.2.48

cross-fetch 4.0.0

msw 1.3.2

react ^16.13.1 || ^17.0.0 || ^18.0.0

react-dom ^16.13.1 || ^17.0.0 || ^18.0.0

react-router-dom ^6.0.0

plugins/argocd/package.json

@kubernetes/client-node ^0.20.0

@material-ui/core ^4.9.13

@material-ui/icons ^4.9.1

@material-ui/lab ^4.0.0-alpha.61

@patternfly/patternfly ^5.1.0

@patternfly/react-charts ^7.1.1

@patternfly/react-core ^5.1.2

@patternfly/react-icons ^5.1.1

@patternfly/react-tokens ^5.1.2

moment ^2.30.1

react-use 17.4.0

@playwright/test 1.41.2

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.0.0

@testing-library/react 14.0.0

@testing-library/user-event 14.0.0

msw 1.0.0

react ^16.13.1 || ^17.0.0 || ^18.0.0

react-router-dom ^6.3.0

plugins/bulk-import/package.json

@material-ui/core ^4.9.13

@material-ui/icons ^4.9.1

@material-ui/lab ^4.0.0-alpha.61

@mui/icons-material 5.14.11

@mui/material ^5.12.2

formik ^2.4.5

lodash ^4.17.21

react-use ^17.2.4

@playwright/test 1.41.2

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.0.0

@testing-library/react 14.0.0

@testing-library/user-event 14.0.0

msw 1.0.0

react 16.13.1 || ^17.0.0 || ^18.0.0

react-router-dom ^6.0.0

plugins/dynamic-plugins-info/package.json

@material-table/core ^3.1.0

react-use ^17.4.0

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/user-event 14.5.1

msw 1.3.2

react ^16.13.1 || ^17.0.0 || ^18.0.0

react-router-dom ^6.0.0

plugins/feedback-backend/package.json

@types/express *

axios ^1.6.4

express ^4.17.1

express-promise-router ^4.1.0

knex ^3.1.0

node-fetch ^2.6.7

nodemailer ^6.9.8

short-uuid ^4.2.2

winston ^3.2.1

yn ^4.0.0

@types/nodemailer 6.4.14

@types/supertest 2.0.12

msw 1.3.2

supertest 6.2.4

plugins/feedback/package.json

@material-ui/core ^4.9.13

@material-ui/icons ^4.9.1

@material-ui/lab ^4.0.0-alpha.61

@one-platform/opc-feedback 0.1.1-alpha

axios ^1.6.4

react-use ^17.2.4

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/user-event 14.0.0

msw 1.0.0

react ^16.13.1 || ^17.0.0 || ^18.0.0

plugins/jfrog-artifactory/package.json

@material-ui/core ^4.9.13

@material-ui/icons ^4.11.3

@material-ui/lab ^4.0.0-alpha.45

react-use ^17.4.0

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/user-event 14.5.1

@types/node 18.18.5

msw 1.3.2

cross-fetch 4.0.0

react ^16.13.1 || ^17.0.0 || ^18.0.0

react-dom ^16.13.1 || ^17.0.0 || ^18.0.0

plugins/keycloak-backend/package.json

lodash ^4.17.21

uuid ^9.0.1

winston ^3.11.0

@types/lodash 4.14.200

@types/supertest 2.0.16

@types/uuid 9.0.5

deepmerge 4.3.1

express 4.19.2

luxon 3.4.4

msw 1.3.2

opener 1.5.2

supertest 6.3.3

plugins/kiali-backend/package.json

axios ^1.6.0

express ^4.18.2

express-promise-router ^4.1.1

moment ^2.29.4

winston ^3.11.0

yn ^4.0.0

@types/express 4.17.20

@types/supertest 2.0.16

msw 1.3.2

supertest 6.3.3

plugins/kiali/package.json

@material-ui/core ^4.9.13

@material-ui/icons ^4.11.3

@material-ui/lab ^4.0.0-alpha.45

@mui/icons-material ^5.15.8

@patternfly/patternfly ^5.1.0

@patternfly/react-charts ^7.1.1

@patternfly/react-core ^5.1.1

@patternfly/react-icons ^5.1.1

@types/regression ^2.0.6

ace-builds ^1.32.7

axios ^1.5.1

cytoscape 3.15.5

d3-format ^3.1.0

deep-freeze 0.0.1

history ^5.3.0

js-yaml ^3.13.1

json-beautify 1.0.1

lodash ^4.17.21

micro-memoize 4.0.9

moment ^2.29.4

prop-types ^15.8.1

react-ace 9.1.3

react-copy-to-clipboard 5.x

react-use ^17.4.0

react-virtualized 9.x

regression ^2.0.1

screenfull 5.0.2

typesafe-actions ^4.2.1

typestyle ^2.4.0

victory-box-plot ^36.9.1

victory-core ^36.9.1

victory-voronoi-container ^36.9.1

@playwright/test 1.41.2

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/user-event 14.5.1

@types/node 20.2.5

@types/react-copy-to-clipboard 5.0.6

cross-fetch 4.0.0

jest-canvas-mock 2.5.2

msw 1.3.2

react-ace 9.1.3

react ^16.13.1 || ^17.0.0 || ^18.0.0

react-dom ^16.13.1 || ^17.0.0 || ^18.0.0

react-router-dom ^6.0.0

plugins/kubernetes-actions/package.json

@kubernetes/client-node ^0.20.0

msw 1.3.2

plugins/matomo-backend/package.json

@types/express 4.17.20

express ^4.18.2

express-promise-router ^4.1.1

http-proxy-middleware ^2.0.6

node-fetch ^3.3.2

winston ^3.11.0

yn ^4.0.0

@types/supertest 2.0.16

msw 1.3.2

supertest 6.3.3

plugins/matomo/package.json

@material-ui/core ^4.9.13

@material-ui/icons ^4.11.3

@material-ui/lab ^4.0.0-alpha.45

@tanstack/react-query ^4.36.1

axios ^1.6.0

react-use ^17.4.0

recharts ^2.9.0

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/user-event 14.5.1

@types/node 18.18.5

cross-fetch 4.0.0

msw 1.3.2

react ^16.13.1 || ^17.0.0 || ^18.0.0

plugins/nexus-repository-manager/package.json

@material-ui/core ^4.9.13

@material-ui/icons ^4.11.3

@material-ui/lab ^4.0.0-alpha.45

react-use ^17.4.0

@hey-api/openapi-ts 0.34.5

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/react-hooks 8.0.1

@testing-library/user-event 14.5.1

@types/node 18.18.5

cross-fetch 4.0.0

msw 1.3.2

react ^16.13.1 || ^17.0.0 || ^18.0.0

react-dom ^16.13.1 || ^17.0.0 || ^18.0.0

react-router-dom ^6.0.0

plugins/notifications-backend/package.json

ajv-formats ^2.1.1

express ^4.18.2

express-promise-router ^4.1.1

knex ^3.0.0

lodash ^4.17.21

node-fetch ^3.3.2

openapi ^1.0.1

openapi-backend ^5.10.5

yn ^4.0.0

@types/express 4.17.20

@types/supertest 2.0.16

js-yaml-cli 0.6.0

knex-mock-client 2.0.1

msw 1.3.2

openapicmd 2.1.0

supertest 6.3.3

plugins/notifications/package.json

@material-table/core ^3.1.0

@material-ui/core ^4.9.13

@material-ui/icons ^4.11.3

@material-ui/lab ^4.0.0-alpha.45

@mui/material ^5.12.2

lodash ^4.17.21

react-relative-time ^0.0.9

react-use ^17.4.0

@openapitools/openapi-generator-cli 2.7.0

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/user-event 14.5.1

@types/node 20.8.7

msw 1.3.2

react ^16.13.1 || ^17.0.0 || ^18.0.0

react-router-dom ^6.0.0

plugins/ocm-backend/package.json

@kubernetes/client-node ^0.20.0

express ^4.18.2

express-promise-router ^4.1.1

semver ^7.5.4

winston ^3.11.0

@types/express 4.17.20

@types/supertest 2.0.16

msw 1.3.2

supertest 6.3.3

plugins/ocm-common/package.json

plugins/ocm/package.json

@material-ui/core ^4.9.13

@material-ui/icons ^4.11.3

@material-ui/lab ^4.0.0-alpha.45

@patternfly/patternfly ^5.1.0

@patternfly/react-icons ^5.1.1

react-use ^17.4.0

semver ^7.5.4

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/user-event 14.5.1

@types/node 18.18.5

cross-fetch 4.0.0

msw 1.3.2

react ^16.13.1 || ^17.0.0 || ^18.0.0

react-dom ^16.13.1 || ^17.0.0 || ^18.0.0

plugins/openshift-image-registry/package.json

@material-ui/core ^4.9.13

@material-ui/icons ^4.11.3

@material-ui/lab ^4.0.0-alpha.45

react-use ^17.4.0

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/user-event 14.5.1

@types/node 18.18.5

msw 1.3.2

cross-fetch 4.0.0

react ^16.13.1 || ^17.0.0 || ^18.0.0

react-dom ^16.13.1 || ^17.0.0 || ^18.0.0

plugins/orchestrator-backend/package.json

@urql/core ^4.1.4

ajv-formats ^2.1.1

cloudevents ^8.0.0

express ^4.18.2

express-promise-router ^4.1.1

fs-extra ^10.1.0

json-schema ^0.4.0

moment ^2.29.4

openapi-backend ^5.10.5

winston ^3.11.0

yn ^5.0.0

@types/express 4.17.20

@types/fs-extra 11.0.1

@types/json-schema 7.0.12

plugins/orchestrator-common/package.json

@severlessworkflow/sdk-typescript ^3.0.3

js-yaml ^4.1.0

json-schema ^0.4.0

plugins/orchestrator-swf-editor-envelope/package.json

@kie-tools-core/editor ^0.32.0

@kie-tools-core/keyboard-shortcuts ^0.32.0

@kie-tools/serverless-workflow-combined-editor ^0.32.0

@kie-tools/serverless-workflow-diagram-editor-assets ^0.32.0

@kie-tools/serverless-workflow-diagram-editor-envelope ^0.32.0

@kie-tools/serverless-workflow-text-editor ^0.32.0

clean-webpack-plugin 4.0.0

css-loader 6.11.0

filemanager-webpack-plugin 8.0.0

html-webpack-plugin 5.6.0

monaco-editor 0.47.0

monaco-editor-webpack-plugin 7.1.0

monaco-yaml 5.1.1

node-polyfill-webpack-plugin 3.0.0

sass 1.74.1

sass-loader 14.1.1

style-loader 3.3.4

terser-webpack-plugin 5.3.10

ts-loader 9.5.1

typescript 5.4.4

webpack 5.91.0

webpack-cli 5.1.4

plugins/orchestrator/package.json

@kie-tools-core/editor ^0.32.0

@kie-tools-core/notifications ^0.32.0

@kie-tools-core/react-hooks ^0.32.0

@kie-tools/serverless-workflow-combined-editor ^0.32.0

@kie-tools/serverless-workflow-language-service ^0.32.0

@kie-tools/serverless-workflow-service-catalog ^0.32.0

@material-ui/core ^4.12.4

@material-ui/icons ^4.11.3

@material-ui/lab ^4.0.0-alpha.45

@monaco-editor/react ^4.6.0

@mui/icons-material ^5.15.3

@rjsf/core ^5.7.3

@rjsf/material-ui ^5.7.3

@rjsf/utils 5.7.3

@rjsf/validator-ajv8 5.7.3

moment ^2.29.4

monaco-editor ^0.39.0

react-json-view ^1.21.3

react-moment ^1.1.3

react-use ^17.4.0

swr ^2.0.0

uuid ^9.0.1

vscode-languageserver-types ^3.16.0

@redhat-developer/red-hat-developer-hub-theme *

@storybook/preview-api 7.5.3

@storybook/react 7.5.3

@testing-library/react 14.2.1

react 18.3.1

react-dom 18.3.1

react ^16.13.1 || ^17.0.0 || ^18.0.0

react-dom ^16.13.1 || ^17.0.0 || ^18.0.0

react-router-dom ^6.0.0

plugins/quay-actions/package.json

plugins/quay/package.json

@material-ui/core ^4.12.2

@material-ui/icons ^4.11.3

@material-ui/lab 4.0.0-alpha.61

react-use ^17.4.0

@playwright/test 1.41.2

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/react-hooks 8.0.1

@testing-library/user-event 14.5.1

@types/node 18.18.5

cross-fetch 4.0.0

msw 1.3.2

react ^16.13.1 || ^17.0.0 || ^18.0.0

react-dom ^16.13.1 || ^17.0.0 || ^18.0.0

react-router-dom ^6.0.0

plugins/rbac-backend/package.json

@dagrejs/graphlib ^2.1.13

casbin ^5.27.1

chokidar ^3.6.0

csv-parse ^5.5.5

express ^4.18.2

express-promise-router ^4.1.1

knex ^3.0.0

lodash ^4.17.21

qs ^6.11.2

typeorm-adapter ^1.6.1

winston ^3.11.0

yn ^4.0.0

@types/express 4.17.20

@types/node 18.18.5

@types/supertest 2.0.16

knex-mock-client 2.0.1

msw 1.3.2

supertest 6.3.3

plugins/rbac-common/package.json

plugins/rbac-node/package.json

plugins/rbac/package.json

@material-ui/core ^4.9.13

@material-ui/icons ^4.11.3

@material-ui/lab ^4.0.0-alpha.45

@mui/icons-material 5.14.11

@mui/material ^5.14.18

@rjsf/core ^5.18.2

@rjsf/mui ^5.18.2

@rjsf/utils ^5.18.2

@rjsf/validator-ajv8 ^5.18.2

autosuggest-highlight ^3.3.4

formik ^2.4.5

react-use ^17.4.0

yup ^1.3.2

@playwright/test 1.41.2

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/react-hooks 8.0.1

@testing-library/user-event 14.5.1

@types/autosuggest-highlight 3.2.3

@types/node 18.18.5

msw 1.3.2

react ^16.13.1 || ^17.0.0 || ^18.0.0

react-router-dom ^6.0.0

plugins/regex-actions/package.json

yaml ^2.3.3

zod ^3.22.4

plugins/scaffolder-annotator-action/package.json

fs-extra ^11.2.0

lodash ^4.17.21

yaml ^2.0.0

plugins/servicenow-actions/package.json

abort-controller ^3.0.0

axios ^1.6.8

form-data ^4.0.0

yaml ^2.3.3

zod ^3.22.4

@hey-api/openapi-ts 0.34.5

@types/node-fetch 2.6.6

msw 1.3.2

plugins/shared-react/package.json

@kubernetes/client-node ^0.20.0

classnames ^2.3.2

date-fns ^2.30.0

file-saver ^2.0.5

lodash ^4.17.21

mathjs ^11.11.2

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/user-event 14.5.1

@types/node 18.18.5

@types/file-saver 2.0.6

cross-fetch 4.0.0

msw 1.3.2

react ^16.13.1 || ^17.0.0 || ^18.0.0

plugins/sonarqube-actions/package.json

yaml ^2.3.3

plugins/tekton/package.json

@aonic-ui/pipelines ^1.1.1

@kubernetes/client-node ^0.20.0

@material-ui/core ^4.9.13

@material-ui/icons ^4.11.3

@material-ui/lab ^4.0.0-alpha.45

@patternfly/patternfly ^5.1.0

@patternfly/react-charts ^7.1.1

@patternfly/react-core ^5.1.2

@patternfly/react-icons ^5.1.1

@patternfly/react-tokens ^5.1.2

@patternfly/react-topology ^5.1.0

classnames ^2.3.2

dagre ^0.8.5

lodash ^4.17.21

react-measure ^2.5.2

react-use ^17.4.0

@playwright/test 1.41.2

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/react-hooks 8.0.1

@testing-library/user-event 14.5.1

@types/node 18.18.5

cross-fetch 4.0.0

msw 1.3.2

react ^16.13.1 || ^17.0.0 || ^18.0.0

react-dom ^16.13.1 || ^17.0.0 || ^18.0.0

react-router-dom ^6.0.0

plugins/topology/package.json

@kubernetes/client-node ^0.20.0

@material-ui/core ^4.9.13

@material-ui/icons ^4.11.3

@material-ui/lab ^4.0.0-alpha.45

@patternfly/patternfly ^5.1.0

@patternfly/react-charts ^7.1.1

@patternfly/react-core ^5.1.1

@patternfly/react-icons ^5.1.1

@patternfly/react-styles ^5.1.1

@patternfly/react-tokens ^5.1.1

@patternfly/react-topology ^5.1.0

classnames 2.x

git-url-parse ^13.1.0

js-yaml ^4.1.0

lodash ^4.17.21

react-use ^17.4.0

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/react-hooks 8.0.1

@testing-library/user-event 14.5.1

@types/git-url-parse 9.0.2

@types/node 18.18.5

cross-fetch 4.0.0

msw 1.3.2

react ^16.13.1 || ^17.0.0 || ^18.0.0

react-dom ^16.13.1 || ^17.0.0 || ^18.0.0

react-router-dom ^6.0.0

plugins/web-terminal/package.json

@material-ui/core ^4.9.13

@material-ui/icons ^4.11.3

@material-ui/lab ^4.0.0-alpha.45

react-use ^17.4.0

xterm ^5.3.0

xterm-addon-attach ^0.9.0

xterm-addon-fit ^0.8.0

@redhat-developer/red-hat-developer-hub-theme *

@testing-library/jest-dom 6.4.2

@testing-library/react 14.2.1

@testing-library/user-event 14.5.1

@types/node 18.18.5

cross-fetch 4.0.0

jest-canvas-mock 2.5.2

msw 1.3.2

react ^16.13.1 || ^17.0.0 || ^18.0.0

nvm

.nvmrc

node 20.12.2

Branch 1.0.x

dockerfile

packages/backend/Dockerfile

node 19-bullseye-slim

github-actions

.github/actions/build/action.yaml

actions/setup-node v4

dtinth/setup-github-actions-caching-for-turbo v1

.github/actions/test/action.yaml

actions/setup-node v3

dtinth/setup-github-actions-caching-for-turbo v1

.github/workflows/add-to-project.yaml

janus-idp/.github main

.github/workflows/pr-semantic.yaml

amannn/action-semantic-pull-request v5@c3cd5d1ea3580753008872425915e343e351ab54

marocchino/sticky-pull-request-comment v2@efaaab3fd41a9c3de579aba759d2552635e590fd

marocchino/sticky-pull-request-comment v2@efaaab3fd41a9c3de579aba759d2552635e590fd

.github/workflows/pr-website.yaml

actions/checkout v4

pnpm/action-setup v2

actions/setup-node v4

.github/workflows/pr.yaml

actions/checkout v4

actions/checkout v4

.github/workflows/publish-backend-plugin-manager.yaml

actions/checkout v4

actions/checkout v4

actions/setup-node v4

.github/workflows/push-website.yaml

actions/checkout v4

pnpm/action-setup v2

actions/setup-node v4

peter-evans/repository-dispatch v2

.github/workflows/push.yaml

actions/checkout v4

actions/checkout v4

npm

package.json

@ianvs/prettier-plugin-sort-imports 4.1.1

@semantic-release/changelog 6.0.3

@semantic-release/exec 6.0.3

@semantic-release/git 10.0.1

@semantic-release/github 9.2.1

@semrel-extra/npm 1.2.2

@spotify/prettier-config 15.0.0

conventional-changelog-conventionalcommits 6.1.0

husky 8.0.3

eslint-plugin-jest 27.4.2

lint-staged 15.0.1

multi-semantic-release 3.0.2

prettier 3.0.3

turbo 1.10.15

typescript 5.2.2

node 18

@types/react ^17.0.68

@types/react-dom ^17.0.21

packages/app/package.json

@material-ui/core ^4.12.4

@material-ui/icons ^4.11.3

@openshift/dynamic-plugin-sdk ^4.0.0

@scalprum/core ^0.6.1

@scalprum/react-core ^0.6.1

history ^5.3.0

lodash ^4.17.21

react ^17.0.2

react-dom ^17.0.2

react-router ^6.17.0

react-router-dom ^6.17.0

react-use ^17.4.0

@scalprum/react-test-utils 0.0.4

@testing-library/jest-dom 5.17.0

@testing-library/react 12.1.5

@testing-library/user-event 14.5.1

@types/node 18.18.5

@types/react-dom 17.0.21

cross-env 7.0.3

packages/backend/package.json

@backstage/backend-common ^0.19.8

better-sqlite3 ^9.0.0

dockerode ^4.0.0

express ^4.18.2

express-promise-router ^4.1.1

pg ^8.11.3

winston ^3.11.0

@types/dockerode 3.3.21

@types/express-serve-static-core 4.17.38

@types/express 4.17.20

@types/luxon 3.3.3

packages/cli/package.json

@manypkg/get-packages ^1.1.3

@openshift/dynamic-plugin-sdk-webpack ^3.0.0

@pmmmwh/react-refresh-webpack-plugin ^0.5.7

@rollup/plugin-commonjs ^25.0.4

@rollup/plugin-json ^6.0.0

@rollup/plugin-node-resolve ^15.2.1

@rollup/plugin-yaml ^4.0.0

@svgr/rollup ^8.1.0

@svgr/webpack ^6.5.1

@yarnpkg/lockfile ^1.1.0

@yarnpkg/parsers ^3.0.0-rc.4

bfj ^7.0.2

chalk ^4.0.0

chokidar ^3.3.1

commander ^9.1.0

css-loader ^6.5.1

esbuild ^0.19.0

esbuild-loader ^2.18.0

eslint ^8.49.0

eslint-config-prettier ^8.10.0

eslint-webpack-plugin ^3.2.0

express ^4.18.2

fork-ts-checker-webpack-plugin ^7.0.0-alpha.8

fs-extra ^10.1.0

handlebars ^4.7.7

html-webpack-plugin ^5.3.1

inquirer ^8.2.0

lodash ^4.17.21

mini-css-extract-plugin ^2.4.2

node-libs-browser ^2.2.1

npm-packlist ^5.0.0

ora ^5.3.0

postcss ^8.2.13

process ^0.11.10

react-dev-utils ^12.0.0-next.60

react-refresh ^0.14.0

recursive-readdir ^2.2.2

rollup ^2.78.0

rollup-plugin-dts ^4.0.1

rollup-plugin-esbuild ^4.7.2

rollup-plugin-postcss ^4.0.0

rollup-pluginutils ^2.8.2

semver ^7.5.4

style-loader ^3.3.1

swc-loader ^0.2.3

typescript-json-schema ^0.62.0

webpack ^5.89.0

webpack-dev-server ^4.15.1

yml-loader ^2.1.0

yn ^4.0.0

@backstage/backend-common 0.19.8

@types/express 4.17.20

@types/fs-extra 9.0.1

@types/inquirer 8.1.3

@types/mock-fs 4.13.3

@types/node 18.18.5

@types/npm-packlist 3.0.0

Check this box to trigger a request for Renovate to run again on this repository

🔌 Plugin: Keycloak

Goal

This epic aims to develop a new Backstage UI plugin in the Janus repo. This UI plugin should integrate Keycloak into Backstage to enable Keycloak user and group entities to be used in the standard Backstage catalog model.

What problem does this solve?

Although Backstage contains the functionality to connect to external identity providers to enable authentication and apply proper RBAC, there is no integration point with Keycloak authentication today.

Requirements

Plugin
Test plan
Installation documentation
End user documentation

Issues in Epic

Stakeholder sign-off

QE
Doc

Additional context
Add any other context or screenshots about the feature request here.

App Topology - Topology view in backstage plugin should update based on selected theme (Dark/Light/System)

Description
As a user, I want to view the topology in the theme as set by the user in the settings i.e Dark, Light, System

Acceptance Criteria

Topology view in the backstage plugin should be shown as the selected theme in backstage
Push the code to GitHub and any changes need to be documented as required.(Needs to check on with GitHub repo)

Additional Details:

Reminder: Upgrade keycloak client once Backstage supports ESM

Keycloak admin client drops support for CommonJS by v19. It's ESM only, causing headaches to many folks:
keycloak/keycloak-nodejs-admin-client#523

However the decision is that they won't introduce CommonJS back. Our only hope is for Backstage to fully support ESM.

backstage/backstage#7011
backstage/backstage#8242
backstage/backstage#12218

Is your feature request related to a problem? Please describe.
Kuberentes plugin dependency may not be desired for multiple reasons:

Adding a cluster to kubernetes plugin expects workload discovery on the cluster. If this is not permitted by a role, Backstage raises errors. Discovering workloads on the Hub cluster may not be desired.
Accessing the Hub requires ServiceAccount access - it's accessed by the backend server at all times, therefore no identity provider can be used. That results in no RBAC applied, all users see the same/all data from the Hub cluster via Kuberentes plugin.

Describe the solution you'd like
Provide a different connection method. Consider changing the config schema to a partial of kubernetes-backend cluster type:

# app-config.yaml
ocm:
  # either use kubernetes
  name: # required if url not defined, string, current setup - match a cluster from kuberenetes plugin config
  # if name is not defined, use direct setup
  url: # required if name not defined, string, hub cluster api endpoint
  skipTLSVerify: # optional, bool, defaults to false
  skipMetricsLookup: # optional, bool, defaults to false
  caData: # optional, str, defaults to null
  caFile: # optional, str, defaults to null

Describe alternatives you've considered
N/A

Additional context
N/A

🔌 Plugin: Multi cluster

Goal

The goal of this epic is to develop a new Backstage plugin in the Janus repo. The goal is to integrate the Backstage instance with Open Cluster Management's MultiClusterHub and MultiCluster Engine.

Acceptance Criteria

All Clusters in the MultiCluterHub should be available in the Backstage catalog.
Users should be able to see the current cluster status
When looking at the cluster entity page, users should be able to see the cluster details, including the OpenShift Console link, OCM console link, OCP and Kubernetes version
When looking at the cluster entity page, users should be able to see the available compute resources

Requirements

Plugin
Test plan
Installation documentation
End user documentation

Issues in Epic

Additional context
Add any other context or screenshots about the feature request here.

Stakeholder sign-off

QE
Doc

Reminder: Upgrade to React v18 once possible

React v18 is not yet supported by Backstage backstage/backstage#12252

Reopen following PRs once this becomes an option:

fix(quay): Format date, size and Manifest information to be same as on the quay UI

The "LAST MODIFIED" field is showing a full timestamp "Thu, 23 Jun 2022 20:31:28 -0000" and should be like this "Jun 23, 2022, 4:31 PM" as the Quay interface show.

The SIZE is on bytes like this "1656016288" and should be MB or GB according to a calculation.

MANIFEST value should be a substring(0, 19) instead of the all value

🔌 Plugin: KubeVirt

🔖 Summary

Create common KubeVirt VMs (basede on instanceTypes) for common OSses (RHEL 8 + 9)

🌐 Project website (if applicable)

https://kubevirt.io

✌️ Context

The goal of such a plugin would be to establish golden paths for VM creation based on two pillars:

instanceTypes - a high levle VM api
golden images - vendor/community maintained golden images for operating systems, ready to use by a user

👀 Have you spent some time to check if this plugin request has been raised before?

I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

I have read the Contributing Guidelines

Are you willing to submit PR?

None

App Topology - Integrate k8s plugin with topology plugin

Description:
Based on the evaluation story - #91 integrate k8s plugin with topology plugin and use its api to get the entity's k8s resources from the associated cluster.

Acceptance Criteria:

Integrate k8s plugin with topology plugin
Use k8s plugin api to get the resources
Refactor data model/transform utils

🔌 Plugin: Tekton

Goal

This epic aims to develop a new Backstage UI plugin in the Janus repo. This UI plugin should provide Backstage users with the ability to see the detailed status of the tekton pipeline associated with a service. They should also be able to view detailed logs of the tekton pipeline associated with a service.

Evaluate existing community plugin to find issues and opportunities for improvement & enhancement

What problem does this solve? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Use cases
A clear and concise description of persona and associated use cases that need to be supported.

Acceptance criteria

Evaluate the plugin, using this BS Plugin Evaluation Templates

Additional context
Add any other context or screenshots about the feature request here.

Issues in Epic

Stakeholder sign-off

QE
Doc

🔌 Plugin: Pipelines as code

Goal
Provide a plugin to enable users to see that a git repo is configured for PAC, and is able to view the PLR, associated Task Runs and logs.

What problem does this solve? Please describe.
-- tbd --

Use cases
As a backstage user, I want easy access to the the status of the PLR execution when triggered by a Pull Request or a Push

Acceptance criteria
-- tbd --

Additional context
Pipelines as Code

Spike review: GitOps

Goal

Once #84 is complete, review the plugin evaluation document and map out the next steps.

Spike: Kubernetes plugin

Goal
Evaluate existing community plugin to find issues and opportunities for improvement & enhancement

What problem does this solve? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Use cases
A clear and concise description of persona and associated use cases that need to be supported.

Acceptance criteria
A clear and concise list of acceptance criteria, noting what will be delivered as part of this epic. This will help identify associated testing, documentation and support needs.

Additional context
Add any other context or screenshots about the feature request here.

Cannot install Keycloak-backend

Describe the bug
Cannot install the Keycloak plugin as the plugin cannot be found

To Reproduce
Steps to reproduce the behavior:

Execute the command from the documentation:

yarn add --cwd packages/backend @janus-idp/keycloak-backend

Getting this error

error An unexpected error occurred: "https://registry.yarnpkg.com/@janus-idp%2fkeycloak-backend: Not found".

Expected behavior
I should be able to install the plugin

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
It works using:

yarn add --cwd packages/backend @janus-idp/backstage-plugin-keycloak-backend

Namespace as a service plugin ( Self service )

Goal
Create a plugin which supports namespace as a service on a dev cluster.

What problem does this solve? Please describe.
Self service is an issue for developers. Getting access to a K8S project is a blocker, thus are unable to easily deploy their application without help from others.

Use cases
A clear and concise description of persona and associated use cases that need to be supported.

Acceptance criteria
A clear and concise list of acceptance criteria, noting what will be delivered as part of this epic. This will help identify associated testing, documentation and support needs.

Additional context
Problem statement document from Raffaele including some of these concepts, as well as namespace-configuration-operator, a configuration example can be found here.

App Topology - Evaluate connecting Topology (backstage plugin) with cluster

Description
As a developer, I want to visualize resources of Deployment kind and Deployment Config Kind with pods ring demonstrating pod status and decorators for the route in a sample plugin for topology as Read-only. This will require connecting with the cluster and evaluating if we can list/watch k8s resources from the cluster, if not what is that needed to get to it?

Acceptance Criteria

evaluating if we can list/watch k8s resources from the cluster
Do we need to use k8s plugin?
Do we need Topology-backend for this?

🔌 Update Janus Tekton plugin to include new UI

Goal

Based off the initial Tekton plugin in the Janus repo, incorporate the PLR viz from the OpenShift Console into the UI plugin.

What problem does this solve

I'd like to see detailed status of the tekton pipeline which associated with a service.

Notes

OUTSTANDING - we need a more comprehensive UX design of where/how we want this to be shown inside of Backstage

Acceptance criteria

I should be able to see the latest PLR viz in the CI/CD tab of a service which has a Tekton Pipeline associated with it.

Additional context

🔌 Plugin: OCI Registry (JFrog)

Goal

This epic aims to develop a new Backstage plugin in the Janus repo. This plugin should allow Backstage users to view details of an image related to a catalog resource deployed from your JFrog Artifactory repository.

Acceptance criteria

Users should be able to view the tags, last update and SHA of an image related to a catalog deployed by a JFrog image

Requirements

Plugin
Test plan
Installation documentation
End user documentation

Issues in Epic

#559 [Doc]
#558 [QE]

Notes

There is a question as to if there should be an OCI Registry frontend plugin which has a number of backend plugins (Quay, ECR, GCR, Nexus, JFrog)

Additional context
Add any other context or screenshots about the feature request here.

🔌 Plugin: OCI Registry (GCR)

Goal

This epic aims to develop a new Backstage plugin in the Janus repo. This plugin should allow Backstage users to view details of an image related to a catalog resource deployed from your Google Cloud Container Registry (GCR).

Acceptance criteria

Users should be able to view the tags, last update and SHA of an image related to a catalog deployed by a GCR image

Requirements

Plugin
Test plan
Installation documentation
End user documentation

Issues in Epic

tbd

Notes

There is a question as to if there should be an OCI Registry frontend plugin which has a number of backend plugins (Quay, ECR, GCR, Nexus, JFrog)

Additional context
Add any other context or screenshots about the feature request here.

OCM: Status indicator is not scaled properly in the latest backstage version

Describe the bug
The status indicator for the OCM plugin clusters is not scaled properly in the ClusterStatusCard and ClusterStatusPage components.

To Reproduce
Steps to reproduce the behavior:

Create/use an up to date backstage app and install the ocm frontend/backend plugins.
Go to the Cluster Status Page
See that the indicator is not scaling properly

Expected behavior
The status indicator should be scaled properly (it should be bigger).

Screenshots
Older backstage version:

Up to date backstage version:

Additional context

🔌 Plugin: Learning paths plugin

Goal

The goal of this epic is to develop a new Backstage UI plugin in the Janus repo. This UI plugin will provide the ability for application developers using Backstage to easily access OpenShift learning paths.

Use cases

As an application developer, I want easy access to the OpenShift Learning Paths that are available on the Developer Sandbox

Acceptance criteria
A clear and concise list of acceptance criteria, noting what will be delivered as part of this epic. This will help identify associated testing, documentation and support needs.

Notes

Need to investigate a phased approach
Phase 1 - tile with a link to https://developers.redhat.com/learn
Phase 2 - Catalog of learning paths available from within Backstage, so developers are able to see what's available easily without having to exit Backstage. Clicking on the tile in the catalog will invoke the Learning Path outside of the Backstage portal.

UI Review of OCM UI plugin

Goal

Review the upstream OCM UI plugin (do we need a template for this?):

Why

Review the UI and user experience associated with this UI plugin to identify gaps before milestone as well as add possible backlog items for the future.

Acceptance Criteria

Identify and add GH stories needed before this epic is considered "complete" from a UI/UX perspective for Milestone 01 (tag with appropriate milestone & include in #54
Identify and add GH stories, considered as enhancements, from a UI/UX perspective, which can be accomplished before Milestone 01

🔌 Plugin: Sarif Viewer

Goal
Provide a Sarif Viewer plugin

What problem does this solve? Please describe.
-- tbd --

Use cases
-- tbd --

Acceptance criteria

Evaluate the plugin, using this BS Plugin Evaluation Templates

Additional information
Deck

🔌 Plugin: Tekton, v2

Goal

Enhance the Janus UI plugin for Tekton Pipelines. Incorporate the PLR log viewer from the OpenShift Console into the UI plugin.

What problem does this solve

I'd like to see detailed logs of the tekton pipeline which associated with a service.

Acceptance criteria

I should be able to access the Task Run logs of the PLR.
I should be able to click on the PLR viz, and be navigated directly to the Task Run log in context in the PLR log viewer.

Additional context

Issues in Epic

🔌 Plugin: Pelorus plugin

Goal

The goal of this epic is to develop a new Backstage UI plugin in the Janus repo. This UI plugin will provide the ability to display DORA metrics based on pelorus.

What problem does this solve? Please describe.
-- tbd --

Use cases
As an application developer using the Backstage portal, I would like to view metrics about the overall software delivery performance of my service including:

Lead time for change
Deployment frequency
Mean time to restore
Change failure rate

Acceptance criteria

tbd

Additional information
Pelorus documentation

Test topology plugin with minikube cluster

Description:
Test minikube cluster with topology-plugin to check if it works fine with it.

🔌 Plugin: OCI Registry (ECR)

Goal

This epic aims to develop a new Backstage plugin in the Janus repo. This plugin should allow Backstage users to view details of an image related to a catalog resource deployed from your Amazon Elastic Container Registry (ECR).

Acceptance criteria

Users should be able to view the tags, last update and SHA of an image related to a catalog deployed by a ECR image

Requirements

Plugin
Test plan
Installation documentation
End user documentation

Issues in Epic

tbd

Notes

There is a question as to if there should be an OCI Registry frontend plugin which has a number of backend plugins (Quay, ECR, GCR, Nexus, JFrog)

Additional context
Add any other context or screenshots about the feature request here.

Review of OCM plugins

Goal

Review the upstream OCM plugins (do we need a template for this?):

Why

Review features and functionality of this plugin to identify gaps before milestone as well as add possible backlog items for the future.

Acceptance Criteria

Identify and add GH stories needed before this epic is considered "complete" for Milestone 01 (tag with appropriate milestone & include in #54
Identify and add GH stories, considered as enhancements which can be accomplished before Milestone 01

Spike: Explore PatternFly usage with Backstage

Goal
Study how PatternFly and existing PatternFly components can be used with Backstage. Find capabilities, limitations and document them.

What problem does this solve? Please describe.
Existing OpenShift console components such as the topology and pipelines views rely heavily on PatternFly. Backstage on the other hand uses Material UI. To evaluate whether we can reuse existing code, we need to determine if it's possible to use PatternFly in a plugin.

Use cases
As a plugin developer, I want to use PatternFly components in a Backstage plugin so that I can reuse existing code from OpenShift console.

Acceptance criteria
Explore answers the following questions:

Can I use @patternfly/react-core components in a Backstage plugin?
Can PatternFly CSS be contributed from a plugin, or does it have to be added to the root Backstage app?
Does PatternFly CSS break the display of Material UI / Backstage components or layout?
Does Material CSS break display of PatternFly components?
Do the styles clash? Can we theme either PatternFly or Backstage to mitigate the different look and feel?
Can I use the @patternfly/react-topology?
Can I use the @patternfly/react-table?
Can I use the @patternfly/react-charts?
How do we handle dark mode?

Document the findings.

Additional context

Designing for Backstage: https://backstage.io/docs/dls/design
Backstage plugins: https://backstage.io/docs/plugins/
Customizing Backstage look and feel: https://backstage.io/docs/getting-started/app-custom-theme
PatternFly React docs: https://patternfly-react-main.surge.sh/

Spike on GitOps plugin

Goal

Evaluate the upstream Argo plugin, using this BS Plugin Evaluation Templates

UI Review of Quay UI plugin

Goal

Review the upstream Quay UI plugin (do we need a template for this?):

Why

Review the UI and user experience associated with this UI plugin to identify gaps before milestone as well as add possible backlog items for the future.

Acceptance Criteria

Identify and add GH stories needed before this epic is considered "complete" from a UI/UX perspective for Milestone 01 (tag with appropriate milestone & include in #60
Identify and add GH stories, considered as enhancements, from a UI/UX perspective, which can be accomplished before Milestone 01

🔌 Plugin: OCI Registry (Nexus)

Goal

The goal of this epic is to develop a new Backstage plugin in the Janus repo. This plugin should provide Backstage user with the ability to view details of an image related to a catalog resource that was deployed by a Nexus image.

Acceptance criteria

Users should be able to view the tags, last update and SHA of an image related to a catalog deployed by a Nexus image

Requirements

Plugin
Test plan
Installation documentation
End user documentation

Issues in Epic

Notes

There is a question as to if there should be an OCI Registry frontend plugin which has a number of backend plugins (Quay, ECR, GCR, Nexus, JFrog)

Additional context
Add any other context or screenshots about the feature request here.

Create a showcase application and run it

Goal
Create a Backstage showcase application and repository with all the supported plugins available.

The showcase application should be based on backstage-build.
There should be instructions available on deploying the showcase using Backstage Helm. An instance of the showcase should be deployed and available on OperateFirst.

What problem does this solve? Please describe.
It provides a showcase environment for Janus supported plugins and allows the dev team to start from a baseline

** List of Plugins **

Kubernetes Plugin
...

Acceptance criteria

Application is created based on backstage-build and available as a github repo.
Instructions are available for deploying with Helm Chart
An instance is running on OperateFirst and automatically updated with updates.
Work with @christophe-f to use the Janus branding he's used in the Assemble demos.

Issues in Epic

App Topology - Finalize on architecture for Topology-plugin

Description
As a developer, I want to get the ability to list/watch data for k8s resources like Deployment, DeploymentConfi, Service, Route per namespace, label selector, etc

Acceptance Criteria

Finalize the approach needed to have the ability to list/watch data for k8s resources like Deployment, DeploymentConfi, Service, Route per namespace, label selector, etc
Do we need to have a dedicated topology-backend?
What does the topology-backend will do?
Will k8s-plugin for backstage be the prerequisite for the topology backend?
Can we list/watch resources like Deployment, DeploymentConfi, Service, Route per namespace, label selector, etc?
Capture all details in doc

Additional Details:

Check on the outcome of spike #56

This would need discussion / meeting with Architect / Lead / etc and based on the finalized architecture, we would need to have more stories

Refactor: Quay plugin code quality improvements

Look into following suggestions and address them if needed:

#101 (review)_

Code is sometimes a copy-paste from quay source and some decisions are not obvious/not great quality. Let's revisit that.

Spike: Explore PatternFly Topology usage with Backstage

Goal
Study how the PatternFly Topology component can be used with Backstage. Find capabilities, limitations and document them.

What problem does this solve? Please describe.
Our OpenShift Application Topology component is highly desirable by OpenShift Users. We'd like to bring this in as a UI plugin. To evaluate whether we can reuse existing code, we need to first determine if it's possible to use PatternFly Topology in a plugin.

Use cases
As a plugin developer, I want to use PatternFly Topology in a Backstage plugin so that I can reuse existing code from OpenShift console.

Acceptance criteria
Explore answers the following questions:

Can I use @patternfly/react-topology components in a Backstage plugin?
Does Material CSS break display of Topology components?
Do the styles clash? Can we theme either PatternFly or Backstage to mitigate the different look and feel?
Can I use the @patternfly/react-topology?
Document the findings.

** Additional context **

Designing for Backstage: https://backstage.io/docs/dls/design
Backstage plugins: https://backstage.io/docs/plugins/
Customizing Backstage look and feel: https://backstage.io/docs/getting-started/app-custom-theme
PatternFly React docs: https://patternfly-react-main.surge.sh/

UI Review of Topology UI plugin

Goal

Review the upstream Topology UI plugin (do we need a template for this?):

Why

Review the UI and user experience associated with this UI plugin to identify gaps before milestone as well as add possible backlog items for the future.

Acceptance Criteria

Identify and add GH stories needed before this epic is considered "complete" from a UI/UX perspective for Milestone 01 (tag with appropriate milestone & include in #58
Identify and add GH stories, considered as enhancements, from a UI/UX perspective, which can be accomplished before Milestone 01

🔌 Plugin: Quay

Goal

This epic aims to develop a new Backstage UI plugin in the Janus repo. This UI plugin should provide Backstage users with the ability to view the tags, last update, and SHA of the image from the Quay repository associated with the catalog resource.

Acceptance criteria

Users should be able to view the tags, last update and SHA of an image related to a catalog deployed by a Quay image

Requirements

Plugin
Test plan
Installation documentation
End user documentation

Issues in Epic

Stakeholder sign-off

QE
Doc

Spike on Tekton plugin

Goal

Evaluate the upstream Tekton plugin, using this BS Plugin Evaluation Templates

Study Backstage telemetry system

Goal
Study how backstage plugin analytics work. Discuss how it can be integrated with Red Hat telemetry collection.

Study how to enable telemetry in general on an instance of Backstage.

Acceptance criteria

The knowledge of plugging analytics mechanics present at the team.
Create a document that explains how Red Hat telemetry can be enabled for a plugin.
Create a document that explains how telemetry collection be enabled in a Backstage instance.

janus-idp / backstage-plugins Goto Github PK

backstage-plugins's People

Contributors

Stargazers

Watchers

Forkers

backstage-plugins's Issues

Goal

Acceptance Criteria

🔖 Summary

🌐 Project website (if applicable)

✌️ Context

👀 Have you spent some time to check if this plugin request has been raised before?

🏢 Have you read the Code of Conduct?

Are you willing to submit PR?

Goal

Why is this needed?

Acceptance Criteria

Goal

Issues in Epic

Stakeholder sign-off

Reference screenshots from OpenShift Application Topology

Topology graph view

Topology graph view with side panel showing kubernetes details

Topology graph view with side panel showing associated resources

Goals

Reference screenshots from OpenShift Console / OpenShift GitOps plugin

Lists all applications which are "managed by GitOps"

Provides a high level overview of the status of the application as it's deployed across each "environment"

[Dark mode] on the details page and also what happens when there are no commit details for an app

Goal

What problem does this solve? Please describe.

Use cases

Acceptance criteria

Issues in Epic

Goal

Additional context

Screenshots of

Rate-Limited

Open

Ignored or Blocked

Detected dependencies

Goal

What problem does this solve?

Requirements

Issues in Epic

Stakeholder sign-off

Goal

Acceptance Criteria

Requirements

Issues in Epic

Stakeholder sign-off

🔖 Summary

🌐 Project website (if applicable)

✌️ Context

👀 Have you spent some time to check if this plugin request has been raised before?

🏢 Have you read the Code of Conduct?

Are you willing to submit PR?

Goal

Issues in Epic

Stakeholder sign-off

Goal

Goal

What problem does this solve

Notes

Acceptance criteria

Additional context

Goal

Acceptance criteria

Requirements

Issues in Epic

Notes

Goal

Acceptance criteria

Requirements

Issues in Epic

Notes

Goal

Use cases

Notes