@plicity/operator
Create your own build pipeline in OpenShift with Gitlab
1.0.0-alpha.8 • Published 5 years ago
Openshift Packages
@plicity/operator-ui
PLICITY operator UI
@openshift-console/plugin-shared
Console plugin shared code
@openshift-assisted/ui-lib
React component library for the Assisted Installer UI
@openshift-console/dynamic-plugin-sdk
Based on the concept of [webpack module federation](https://webpack.js.org/concepts/module-federation/), dynamic plugins are loaded and interpreted from remote sources at runtime. The standard way to deliver and expose dynamic plugins to Console is throug
@openshift-console/dynamic-plugin-sdk-internal
Based on the concept of [webpack module federation](https://webpack.js.org/concepts/module-federation/), dynamic plugins are loaded and interpreted from remote sources at runtime. The standard way to deliver and expose dynamic plugins to Console is throug
@openshift-console/dynamic-plugin-sdk-internal-kubevirt
Based on the concept of [webpack module federation](https://webpack.js.org/concepts/module-federation/), dynamic plugins are loaded and interpreted from remote sources at runtime. The standard way to deliver and expose dynamic plugins to Console is throug
@openshift-console/dynamic-plugin-sdk-webpack
Based on the concept of [webpack module federation](https://webpack.js.org/concepts/module-federation/), dynamic plugins are loaded and interpreted from remote sources at runtime. The standard way to deliver and expose dynamic plugins to Console is throug
oc-port-forward
Simple OC port forward
rw-ui-lib
React component library for the Assisted Installer UI
rw-dynamic-plugin-sdk
Based on the concept of [webpack module federation](https://webpack.js.org/concepts/module-federation/), dynamic plugins are loaded and interpreted from remote sources at runtime. The standard way to deliver and expose dynamic plugins to Console is throug
rw-dynamic-plugin-sdk-webpack
Based on the concept of [webpack module federation](https://webpack.js.org/concepts/module-federation/), dynamic plugins are loaded and interpreted from remote sources at runtime. The standard way to deliver and expose dynamic plugins to Console is throug
kubernetes-mcp-server
Model Context Protocol (MCP) server for Kubernetes and OpenShift
@theia-extension-tester/openshift-authenticator
Authenticate users into Eclipse Che instances installed from OperatorHub. Used as part of theia-extension-tester.
@vbartoli/skupper-network-console
Skupper network console
alfonsomthd-odftest
ODF console shared code.
ccos-dynamic-plugin-sdk-webpack
Based on the concept of [webpack module federation](https://webpack.js.org/concepts/module-federation/), dynamic plugins are loaded and interpreted from remote sources at runtime. The standard way to deliver and expose dynamic plugins to Console is throug
bcoc
BC Gov wrapper for OpenShift's oc CLI