Skip to content

RHIDP-7849 Added existing modules to _Getting started with RHDH for PE_ #1267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 14 commits into
base: main
Choose a base branch
from

Conversation

themr0c
Copy link
Member

@themr0c themr0c commented Jul 8, 2025

This is a rough outline draft to see how we can leverage existing content to populate the book.

  • Include existing content to the new book.
  • Fix build for broken xrefs, blocks that were not closed properly.
  • For content that cannot be reused as is, write a version that works in getting started context.
  • Authentication is intentionally left out as it belongs to RHIDP-7975 Enabling authentication procedures with mandatory steps only #1266.
  • The intention is to have an opinated Getting Started with all non-negociable configuration to go into production. It doesn't go into details for further customizations.

IMPORTANT: Do Not Merge - To be merged by Docs Team Only

Version(s): 1.7

Issue: https://issues.redhat.com/browse/RHIDP-7849

Preview: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1267/getting-started-with-rhdh-on-ocp-for-the-platform-engineer/

@themr0c themr0c marked this pull request as ready for review July 15, 2025 12:22
@themr0c themr0c requested a review from hmanwani-rh July 15, 2025 12:23
…n-secrets-step-in-getting-started-with-rhdh-on-ocp-for-the-platform-engineer-context.adoc
…n-prerequisites-in-getting-started-with-rhdh-on-ocp-for-the-platform-engineer-context.adoc
Copy link

@deerskindoll deerskindoll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a couple of comments

* Injects environment variables provisioned in your custom secrets.

.Prerequisites
* By using the link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/cli_tools/index#cli-about-cli_cli-developer-commands[{openshift-cli}], you have access, with developer permissions, to the {ocp-short} cluster aimed at containing your {product-short} instance.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* By using the link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/cli_tools/index#cli-about-cli_cli-developer-commands[{openshift-cli}], you have access, with developer permissions, to the {ocp-short} cluster aimed at containing your {product-short} instance.
* You have link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/cli_tools/index#cli-about-cli_cli-developer-commands[{openshift-cli}] installed.
* You have access with developer permissions to the {ocp-short} cluster that should contain your {product-short} instance.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would remove an important piece of information : you have access with the CLI (not with the web console).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see. Is there another way to rewrite it so that the prerequisites match (in this case they should all start with "You...").

= Preparing your external services

{product} relies on external services.
Prepare the required external services.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if the overview of required services wouldn't look and read better as a table

.Procedure
. Author your custom `_<my_product_secrets>_.txt` file to provision your secrets as environment variables values in an {ocp-short} secret, rather than in clear text in your configuration files.
It contains one secret per line in `KEY=value` form.
. For security, store your secrets as environment variables values in an {ocp-short} secret,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this sentence might work better as an admonition

- permission
----
Most fields use environment variables that you defined in secrets in the previous step.
`app`::

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this a table that the preview doesn't display correctly?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

description list

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

consider using a table instead. this feels difficult to read, tables are a bit easier to navigate, imho


** To prepare a deployment with the {product} Operator on {ocp-short}, you can start with an empty file.

** To prepare a deployment with the {product} Helm chart, or on Kubernetes, enter the {product-short} base URL in the relevant fields in your `{my-app-config-file}` file to ensure proper functionality of {product-short}.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd label this as optional since you have to choose between the operator or helm deployment, no?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is unchanged content (just moved to a snippet. The 2 unordered steps denote the user choice (Operator, Helm). See: https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1267/configuring/#provisioning-your-custom-configuration

@@ -0,0 +1,9 @@
.Next steps
Consider provisioning additional config maps and secrets:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what are the benefits? instead of telling the user to consider this step, I'd explain why they should do it

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is unchanged content (just moved to a snippet.

@@ -1,10 +1,53 @@
include::artifacts/attributes.adoc[]
:title: Getting started with {product} on {ocp-brand-name} for the platform engineer
:subtitle: As a platform engineer, prepare your IT infrastructure including {ocp-brand-name} and required external components, and run your first {product} ({product-very-short}) instance in production.
:abstract: As a platform engineer, prepare your IT infrastructure including {ocp-brand-name} and required external components, and run your first {product} ({product-very-short}) instance in production.
:context: customizing-display
:abstract: As a platform engineer, prepare your IT infrastructure including {ocp-brand-name} and required external components, and run your first {product} ({product-very-short}) instance in production with an adapted secure, efficient, and resilient configuration.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you have to specify this is a platform engineer procedure? it feels a bit clunky

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is currently under debate in the docs team. I am waiting for the debate conclusion to update it.

[id="{context}"]
= {title}

{abstract}

Adapted::

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if it is because of the titles (adapted, secure etc.) but this section feels confusing.

…n-appconfig-step-in-getting-started-with-rhdh-on-ocp-for-the-platform-engineer-context.adoc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants