Merge branch 'redhat-developer:main' into secure-workflow

Author: Zaperex

artifacts/rhdh-plugins-reference/aap-backend/aap-backend-plugin-readme.adoc

@@ -28,11 +28,11 @@ The AAP backend plugin is pre-loaded in {product-short} with basic configuration
 
 [source,yaml]
 ----
-global: 
-  dynamic: 
-    includes: 
+global:
+  dynamic:
+    includes:
       - dynamic-plugins.default.yaml
-    plugins: 
+    plugins:
       - package: ./dynamic-plugins/dist/janus-idp-backstage-plugin-aap-backend-dynamic
         disabled: false
 ----
@@ -60,9 +60,9 @@ To enable the AAP plugin, you must set the following environment variables:
            owner: <owner>
            system: <system>
            schedule: # optional; same options as in TaskScheduleDefinition
-             # supports cron, ISO duration, "human duration" as used in code
+             # supports cron, ISO 8601 duration strings, and duration objects
              frequency: { minutes: 1 }
-             # supports ISO duration, "human duration" as used in code
+             # supports ISO 8601 duration strings and duration objects
              timeout: { minutes: 1 }
 ----
 --

artifacts/rhdh-plugins-reference/keycloak/keycloak-plugin-admin.adoc

@@ -53,9 +53,9 @@ You can configure a schedule in the `app-config.yaml` file, as follows:
              # ...
              # highlight-add-start
              schedule: # optional; same options as in TaskScheduleDefinition
-               # supports cron, ISO duration, "human duration" as used in code
+               # supports cron, ISO 8601 duration strings, and duration objects
                frequency: { minutes: 1 }
-               # supports ISO duration, "human duration" as used in code
+               # supports ISO 8601 duration strings and duration objects
                timeout: { minutes: 1 }
                initialDelay: { seconds: 15 }
                # highlight-add-end

artifacts/rhdh-plugins-reference/keycloak/keycloak-plugin-readme.adoc

@@ -1,5 +1,5 @@
 [id="rhdh-keycloak_{context}"]
-= Installation and configuration of Keycloak 
+= Installation and configuration of Keycloak
 
 The Keycloak backend plugin, which integrates Keycloak into {product-short}, has the following capabilities:
 
@@ -12,11 +12,11 @@ The Keycloak plugin is pre-loaded in {product-short} with basic configuration pr
 
 [source,yaml]
 ----
-global: 
-  dynamic: 
-    includes: 
+global:
+  dynamic:
+    includes:
       - dynamic-plugins.default.yaml
-    plugins: 
+    plugins:
       - package: ./dynamic-plugins/dist/backstage-community-plugin-catalog-backend-module-keycloak-dynamic
         disabled: false
 ----
@@ -48,9 +48,9 @@ You can configure a schedule in the `app-config.yaml` file, as follows:
              # ...
              # highlight-add-start
              schedule: # optional; same options as in TaskScheduleDefinition
-               # supports cron, ISO duration, "human duration" as used in code
+               # supports cron, ISO 8601 duration strings, and duration objects
                frequency: { minutes: 1 }
-               # supports ISO duration, "human duration" as used in code
+               # supports ISO 8601 duration strings and duration objects
                timeout: { minutes: 1 }
                initialDelay: { seconds: 15 }
                # highlight-add-end

artifacts/rhdh-plugins-reference/ocm/ocm-plugin-readme.adoc

@@ -25,15 +25,15 @@ The Red Hat Plug-ins for Backstage (RHPIB) packages are hosted in a separate NPM
 ----
 # update your .npmrc or .yarnrc file
 yarn config set "@redhat:registry" https://npm.registry.redhat.com
-# then pull a package 
+# then pull a package
 yarn add @redhat/backstage-plugin-quay
 ----
 
-For more information, see link:https://docs.npmjs.com/cli/v9/configuring-npm/npmrc[npm docs]. 
+For more information, see link:https://docs.npmjs.com/cli/v9/configuring-npm/npmrc[npm docs].
 
-Creating a `.npmrc` file ensures that all the packages are scoped under `@redhat` and are fetched from link:https://npm.registry.redhat.com/[Red Hat's NPM registry], while the rest dependencies remain sourced from other link:registry.npmjs.org[registry]. 
+Creating a `.npmrc` file ensures that all the packages are scoped under `@redhat` and are fetched from link:https://npm.registry.redhat.com/[Red Hat's NPM registry], while the rest dependencies remain sourced from other link:registry.npmjs.org[registry].
 
-Using this configuration, you can proceed with the installation of the individual packages. 
+Using this configuration, you can proceed with the installation of the individual packages.
 
 The OCM plugin is composed of two packages, including:
 
@@ -204,9 +204,9 @@ For more information about the configuration, see https://backstage.io/docs/feat
               # ...
               # highlight-add-start
               schedule: # optional; same options as in TaskScheduleDefinition
-                # supports cron, ISO duration, "human duration" as used in code
+                # supports cron, ISO 8601 duration strings, and duration objects
                 frequency: { minutes: 1 }
-                # supports ISO duration, "human duration" as used in code
+                # supports ISO 8601 duration strings and duration objects
                 timeout: { minutes: 1 }
               # highlight-add-end
 +
@@ -295,7 +295,7 @@ yarn workspace app add @redhat/backstage-plugin-ocm
 --
 
 . Select the components that you want to use, such as:
- 
+
 ** `OcmPage`: This is a standalone page or dashboard displaying all clusters as tiles. You can add `OcmPage` to `packages/app/src/App.tsx` file as follows:
 +
 --

assemblies/assembly-centralizing-your-software-components-in-rhdh.adoc

@@ -24,9 +24,9 @@ include::modules/centralizing-your-software-components-in-rhdh/proc-registering-
 
 include::modules/centralizing-your-software-components-in-rhdh/proc-updating-existing-components-in-your-rhdh-catalog.adoc[leveloffset=+1]
 
-include::modules/centralizing-your-software-components-in-rhdh/proc-finding-the-right-components-quickly-in-the-rhdh-catalog-by-kind.adoc[leveloffset=+1]
+include::modules/centralizing-your-software-components-in-rhdh/proc-finding-components-by-kind-in-the-rhdh-catalog.adoc[leveloffset=+1]
 
-include::modules/centralizing-your-software-components-in-rhdh/proc-finding-the-right-components-quickly-in-the-rhdh-catalog-by-using-the-filter-field.adoc[leveloffset=+1]
+include::modules/centralizing-your-software-components-in-rhdh/proc-filtering-components-by-text-in-the-rhdh-catalog.adoc[leveloffset=+1]
 
 include::modules/centralizing-your-software-components-in-rhdh/proc-reviewing-the-yaml-configuration-of-your-rhdh-software-catalog.adoc[leveloffset=+1]
 

assemblies/assembly-importing-and-using-an-existing-template-for-faster-development.adoc

@@ -14,7 +14,7 @@ include::modules/importing-and-using-an-existing-template-for-faster-development
 
 include::modules/importing-and-using-an-existing-template-for-faster-development/ref-creating-templates.adoc[leveloffset=+1]
 
-include::modules/importing-and-using-an-existing-template-for-faster-development/proc-creating-a-new-software-component-using-templates.adoc[leveloffset=+1]
+include::modules/importing-and-using-an-existing-template-for-faster-development/proc-creating-a-software-component-using-templates.adoc[leveloffset=+1]
 
 include::modules/importing-and-using-an-existing-template-for-faster-development/proc-searching-and-filtering-software-templates.adoc[leveloffset=+1]
 

assemblies/assembly-rhdh-default-configuration.adoc

@@ -19,4 +19,6 @@ include::modules/configuring-external-databases/con-mounts-for-default-secret-pv
 
 include::modules/configuring-external-databases/proc-configuring-mount-paths.adoc[leveloffset=+2]
 
-include::modules/configuring-external-databases/proc-mounting-to-specific-containers.adoc[leveloffset=+2]
+include::modules/configuring-external-databases/proc-mounting-to-specific-containers.adoc[leveloffset=+2]
+
+include::modules/configuring/ref-time-syntax.adoc[leveloffset=1]

assemblies/assembly-using-developer-lightspeed.adoc

@@ -11,7 +11,27 @@ endif::[]
 
 :context: Using-developer-lightspeed
 
-{ls-brand-name} is designed to support you when performing various tasks during your development workflow.
+{ls-brand-name} is designed to help you perform development tasks through a conversational interface. You can ask questions, analyze logs, generate code, and create test plans.
+
+.Capabilities
+The scope of questions you can ask depends on your configuration:
+
+* *Question Validation* enabled (default): Supports general questions about {product}. For example:
+
+** “Tell me about {product}.”
+** “What are the benefits of {product-very-short}?”
+** “Can I use {product-very-short} on an {ocp-short}?”
+** “How do I install plugins on {product}?”
+
+* *Question Validation* disabled: Supports broader tasks such as log analysis, code generation, and creating Kubernetes deployments. For example:
+
+** “Analyze this log for me…”
+** “Suggest libraries and frameworks I can use to build Event Driven Architecture microservices.”
+** “I'm not familiar with this language, so explain to me what this code snippet is doing…”
+** “Create a Kubernetes deployment for this service…”
+** “Create a test plan for the following scenarios and conditions…”
+** “Create a Jira record that describes the following feature…”
+** “Draft the end-user documentation describing how to use the following cli command…”
 
 [NOTE]
 ====
@@ -22,36 +42,14 @@ The `Question Validation` feature is enabled by default if you are using the `qu
 * `External_providers_dir` set to `null` 
 ====
 
-With `Question Validation` enabled, you can ask {ls-short} the following types of questions:
-
-* “Tell me about {product}.”
-
-* “What are the benefits of {product-very-short}?”
-
-* “Can I use {product-very-short} on an {ocp-short}?”
-
-* “How do I install plugins on {product}?”
-
-With `Question Validation` disabled, the scope of prompts you can put to {ls-short} is much broader. This allows {ls-short} to support you in a much more varied range of work situations as described in the following examples:
-
-* “Analyze this log for me…”
-
-* “Suggest libraries and frameworks I can use to build Event Driven Architecture microservices.”
-
-* “I'm not familiar with this language, so explain to me what this code snippet is doing…”
-
-* “Create a Kubernetes deployment for this service…”
-
-* “Create a test plan for the following scenarios and conditions…”
-
-* “Create a Jira record that describes the following feature…”
+.Prerequisites
 
-* “Draft the end-user documentation describing how to use the following cli command…”
+* You have the {ls-short} plugin configured in your {product-very-short} instance.
 
-include::modules/developer-lightspeed/proc-using-developer-lightspeed-to-start-a-chat-for-the-first-time.adoc[leveloffset=+1]
+include::modules/developer-lightspeed/proc-starting-a-chat-in-developer-lightspeed.adoc[leveloffset=+1]
 
-include::modules/developer-lightspeed/proc-using-developer-lightspeed-to-create-new-chats-after-the-first-chat.adoc[leveloffset=+1]
+include::modules/developer-lightspeed/proc-starting-a-chat-in-developer-lightspeed-after-the-first-time.adoc[leveloffset=+1]
 
-include::modules/developer-lightspeed/proc-using-developer-lightspeed-to-view-chat-history.adoc[leveloffset=+1]
+include::modules/developer-lightspeed/proc-viewing-chat-history-in-developer-lightspeed.adoc[leveloffset=+1]
 
-include::modules/developer-lightspeed/proc-using-developer-lightspeed-to-delete-a-chat.adoc[leveloffset=+1]
+include::modules/developer-lightspeed/proc-deleting-a-chat-in-developer-lightspeed.adoc[leveloffset=+1]

modules/centralizing-your-software-components-in-rhdh/proc-filtering-components-by-text-in-the-rhdh-catalog.adoc

@@ -0,0 +1,15 @@
+// Module included in the following assemblies:
+//
+// * assemblies/assembly-about-software-catalogs.adoc
+:_mod-docs-content-type: PROCEDURE
+[id="proc-filtering-components-by-text-in-the-rhdh-catalog_{context}"]
+= Filtering components by text in the {product} Catalog
+
+Use this procedure to search and filter components by text in the Software Catalog.
+
+.Procedure
+. In your {product} navigation menu, click *Catalog*.
+. In the *Search* field, enter a component name, description, or keyword that you are looking for.
+
+.Verification
+* The *Catalog* list updates to display only components matching your search criteria.

modules/centralizing-your-software-components-in-rhdh/proc-finding-components-by-kind-in-the-rhdh-catalog.adoc

@@ -0,0 +1,21 @@
+:_mod-docs-content-type: PROCEDURE
+[id="proc-finding-components-by-kind-in-the-rhdh-catalog_{context}"]
+= Finding components by Kind in the {product} catalog
+
+Use this procedure to filter the Software Catalog to display components by their type.
+
+.Prerequisites
+* You are logged in to the {product-very-short} instance.
+
+.Procedure
+. In your {product} navigation menu, click *Catalog*.
+. On the *Catalog* page, click the *Kind* drop-down list.
+. Select the *Kind* you want to filter by, such as *Component*, *API*, or *Template*.
++
+[NOTE]
+====
+The available filter lists change based on the *Kind* you select, showing options relevant to that entity type.
+====
+
+.Verification
+* The Catalog updates to list only the components matching the selected *Kind*.