Merge branch 'main' into RHIDP-7975

Signed-off-by: Fabrice Flore-Thébault <[email protected]>

Author: themr0c

assemblies/assembly-enabling-authentication-with-mandatory-steps-only.adoc

@@ -1,5 +1,5 @@
 :_mod-docs-content-type: ASSEMBLY
-:only-default-steps:
+:optional-steps: disable
 
 [id='enabling-authentication-with-mandatory-steps-only']
 = Enabling authentication in {product} (with mandatory steps only)

assemblies/assembly-enabling-authentication.adoc

@@ -1,11 +1,9 @@
 :_mod-docs-content-type: ASSEMBLY
+:optional-steps: enable
 
 [id='enabling-authentication']
 = Enabling authentication in {product}
 
-
-
-
 include::modules/authentication/con-understanding-authentication-and-user-provisioning.adoc[leveloffset=+1]
 
 

modules/authentication/proc-enabling-user-authentication-with-github.adoc

@@ -113,7 +113,7 @@ Enter your schedule timeout, in the ISO duration or "human duration" format.
 Enter your schedule initial delay, in the ISO duration or "human duration" format.
 --
 
-. To set up the GitHub authentication provider, add the `auth.providers.github` section to the `{my-app-config-file}` file content:
+. To set up the GitHub authentication provider, add the `auth.providers.github` section to your `{my-app-config-file}` file:
 +
 --
 .`{my-app-config-file}` file fragment with mandatory fields to enable authentication with GitHub
@@ -140,11 +140,13 @@ Enter the configured secret variable name: `$\{GITHUB_CLIENT_SECRET}`.
 
 `signInPage`::
 Enter `github` to enable the GitHub provider as your {product-short} sign-in provider.
-
-ifndef::only-default-steps[]
-Optional: Consider adding the following optional fields:
-
-.`{my-app-config-file}` file fragment including optional fields to enable authentication with GitHub
++
+Optional: Consider adding optional fields.
+ifeval::[{optional-steps} == 'disable']
+See {configuring-book-link}[{configuring-book-title}].
+endif::[]
+ifeval::[{optional-steps} == 'enable']
++
 [source,yaml,subs="+quotes"]
 ----
 auth:

modules/authentication/proc-enabling-user-authentication-with-microsoft-azure.adoc

@@ -97,7 +97,6 @@ include::{docdir}/artifacts/snip-technology-preview.adoc[]
 
 . To provision {azure-short} users and groups to the {product-short} software catalog, add the `catalog.providers.microsoftGraphOrg` section to your custom {product-short} `{my-app-config-file}` configuration file:
 +
---
 [id=microsoftGraphOrgProviderId]
 .`{my-app-config-file}` fragment with mandatory `microsoftGraphOrg` fields
 [source,yaml]
@@ -144,10 +143,12 @@ In a large organization, user provisioning might take a long time, therefore avo
 
 `initialDelay`:::
 Enter the schedule initial delay in the ISO duration or human duration format.
-
-ifndef::only-default-steps[]
-Optional: Consider adding the following optional `microsoftGraphOrg.providerId` fields:
-
++
+Optional: Consider adding optional fields.
+ifeval::[{optional-steps} == 'disable']
+See {configuring-book-link}[{configuring-book-title}].
+endif::[]
+ifeval::[{optional-steps} == 'enable']
 [id=authority]
 `authority`::
 Enter your link:https://learn.microsoft.com/en-us/graph/deployments#app-registration-and-token-service-root-endpoints[{azure-short} authority URL], when different from the default: `\https://login.microsoftonline.com`.
@@ -340,7 +341,6 @@ catalog:
 `group.select`::
 Enter the link:https://learn.microsoft.com/en-us/graph/api/resources/schemaextension?view=graph-rest-1.0[Microsoft Graph resource type] list to retrieve.
 +
-.`{my-app-config-file}` fragment with optional `group.select` field
 [source,yaml]
 ----
 catalog:
@@ -350,13 +350,10 @@ catalog:
         group:
           select: ['id', 'displayName', 'description']
 ----
---
 endif::[]
 
 . To set up the {azure-short} authentication provider, add the `auth.providers.microsoft` section to your `{my-app-config-file}` file content:
 +
---
-.`{my-app-config-file}` file fragment with mandatory fields to enable authentication with {azure-short}
 [source,yaml,subs="+quotes,+attributes"]
 ----
 auth:
@@ -385,8 +382,12 @@ Enter the configured secret variable name: `$\{AUTHENTICATION_AZURE_TENANT_ID}`.
 
 `signInPage`::
 Enter `microsoft` to set the {azure-short} provider as your {product-short} sign-in provider.
-
-Optional: Consider adding following optional fields:
++
+Optional: Consider adding optional fields.
+ifeval::[{optional-steps} == 'disable']
+See {configuring-book-link}[{configuring-book-title}].
+endif::[]
+ifeval::[{optional-steps} == 'enable']
 
 `domainHint`::
 Optional for single-tenant applications.
@@ -486,7 +487,6 @@ This resolver looks up the user by matching their Microsoft email to the user en
 Configure the sign-in resolver to bypass the user provisioning requirement in the {product-short} software catalog.
 +
 WARNING: Use `dangerouslyAllowSignInWithoutUserInCatalog` to explore {product-short} features, but do not use it in production.
---
 
 .Verification
 . To verify user and group provisioning, check the console logs for `MicrosoftGraphOrgEntityProvider` events.

modules/authentication/proc-enabling-user-authentication-with-rhbk.adoc

@@ -51,8 +51,6 @@ plugins:
 ----
 
 . To provision {rhbk} users and groups to the {product-short} software catalog, add the `catalog.providers.keycloakOrg` section to your custom {product-short} `{my-app-config-file}` configuration file:
-
-.. Add mandatory fields:
 +
 [id=keycloakOrgProviderId]
 .`{my-app-config-file}` fragment with mandatory `keycloakOrg` fields
@@ -83,10 +81,12 @@ Enter the realm name to provision users, such as `master`.
 
 `loginRealm`::
 Enter the realm name to authenticate users, such as `master`.
-
-ifndef::only-default-steps[]
-.. Optional: Consider adding optional fields:
-
++
+Optional: Consider adding optional fields.
+ifeval::[{optional-steps} == 'disable']
+See {configuring-book-link}[{configuring-book-title}].
+endif::[]
+ifeval::[{optional-steps} == 'enable']
 `userQuerySize`::
 Enter the user count to query simultaneously.
 Default value: `100`.
@@ -196,9 +196,12 @@ To allow the identity provider to automatically determine whether to prompt for
 ====
 If `prompt: auto` is not set, the identity provider defaults to `prompt: none`, which assumes that you are already logged in and rejects sign-in requests without an active session.
 ====
-
-.. Optional: Consider adding optional fields:
-
++
+Optional: Consider adding optional fields.
+ifeval::[{optional-steps} == 'disable']
+See {configuring-book-link}[{configuring-book-title}].
+endif::[]
+ifeval::[{optional-steps} == 'enable']
 `callbackUrl`::
 {rhbk} callback URL.
 +
@@ -349,6 +352,7 @@ For security, consider that if multiple valid refresh tokens are issued due to f
 . From the *Realm Settings* page, click the *Tokens* tab.
 . From the *Refresh tokens* section of the *Tokens* tab, toggle the *Revoke Refresh Token* to the *Enabled* position.
 ====
+endif::[]
 
 .Verification
 

modules/orchestrator/proc-enable-orchestrator-plugin.adoc

@@ -46,6 +46,19 @@ data:
                           icon: orchestratorIcon
                           text: Orchestrator
                         path: /orchestrator
+                    entityTabs:
+                      - path: /workflows
+                        title: Workflows
+                        mountPoint: entity.page.workflows
+                    mountPoints:
+                      - mountPoint: entity.page.workflows/cards
+                      importName: OrchestratorCatalogTab
+                      config:
+                        layout:
+                          gridColumn: '1 / -1'
+                          if:
+                            anyOf:
+                              - IsOrchestratorCatalogTabAvailable
         - package: "@redhat/[email protected]"
           disabled: false
           pluginConfig:

titles/setting-up-and-configuring-your-first-red-hat-developer-hub-instance/master.adoc

@@ -3,7 +3,7 @@ include::artifacts/attributes.adoc[]
 :subtitle: Prepare your IT infrastructure including {ocp-brand-name} and required external components, and run your first {product} ({product-very-short}) instance in production.
 :abstract: Prepare your IT infrastructure including {ocp-brand-name} and required external components, and run your first {product} ({product-very-short}) instance in production.
 :context: setting-up-and-configuring-your-first-rhdh-instance
-:only-default-steps:
+:optional-steps: disable
 [id="{context}"]
 = {title}