You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This section describes Developer Preview features in the Model Context Protocol plugin. Developer Preview features are not supported by Red Hat in any way and are not functionally complete or production-ready. Do not use Developer Preview features for production or business-critical workloads. Developer Preview features provide early access to functionality in advance of possible inclusion in a Red Hat product offering. Customers can use these features to test functionality and provide feedback during the development process. Developer Preview features might not have any documentation, are subject to change or removal at any time, and have received limited testing. Red Hat might provide ways to submit feedback on Developer Preview features without an associated SLA.
4
+
5
+
For more information about the support scope of Red Hat Developer Preview features, see https://access.redhat.com/support/offerings/devpreview/[Developer Preview Support Scope].
This section describes Developer Preview features in the Scorecard plugin. Developer Preview features are not supported by Red Hat in any way and are not functionally complete or production-ready. Do not use Developer Preview features for production or business-critical workloads. Developer Preview features provide early access to functionality in advance of possible inclusion in a Red Hat product offering. Customers can use these features to test functionality and provide feedback during the development process. Developer Preview features might not have any documentation, are subject to change or removal at any time, and have received limited testing. Red Hat might provide ways to submit feedback on Developer Preview features without an associated SLA.
4
+
5
+
For more information about the support scope of Red Hat Developer Preview features, see https://access.redhat.com/support/offerings/devpreview/[Developer Preview Support Scope].
= Centralizing your software components in the {product} catalog for easier access
6
6
7
7
The {product} Software Catalog is a centralized system that gives you visibility into all the software across your ecosystem, including services, websites, libraries, and data pipelines. You can use it to view ownership details and metadata for each component in one place.
8
8
@@ -16,18 +16,18 @@ The *Overview* page for a component provides key information such as links to th
16
16
17
17
//[Add any Component screenshot of the latest build]
= Installing and configuring Scorecards to view metrics in your {product} instance
5
+
:context: assembly-configuring-scorecards-in-rhdh
6
+
7
+
You can install and configure the following Scorecards to display metrics and visual health status for software components in the {product-very-short} catalog:
Copy file name to clipboardExpand all lines: assemblies/assembly-configuring-templates.adoc
+1-11Lines changed: 1 addition & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,19 +7,9 @@
7
7
Software Templates in {product} provide a streamlined way to create software components and publish them to different version control repositories such as Git.
8
8
Platform engineers create and maintain Software Templates in {product}.
9
9
10
-
You can configure Software Templates to create software components, and publish these components to Git repositories.
11
-
Once the components are published to Git repositories, register these components in the Software Catalog.
12
-
13
-
A template is a form composed of different UI fields that is defined in a YAML file.
14
-
Software Templates include _actions_, which are steps that are executed in sequential order and can be executed conditionally.
0 commit comments