add new rosa cli log forwarder assembly

[jc-berger]

Version(s):

4.20+

Issue:
https://issues.redhat.com/browse/OSDOCS-12691

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

[openshift-ci]

Hi @jc-berger. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[jc-berger]

@bhardesty I'm used to writing commands as [oc, bash]

Looking at the other modules in the ROSA security assemblies, I see they follow the [source, terminal] structure. Maybe because we're using ROSA CLI commands?

Anyway, please let me know what you think is the best way to document command for consistency.

[jc-berger]

@bhardesty I was looking at the attributes and saw the {rosa-short} was rendered as "Rosa with HCP"

Looking at other ROSA docs, I see that we'll sometimes simply write out the acronym, ROSA, so for a command, I thought to be more concise. let me know if we're adamant about always using a prod-name a certain way.

[jc-berger]

@bhardesty as a standard practice, does ROSA keep IDs to match the title perfectly?

Since this is a reference doc, I thought of naming it simply, ROSA CLI commands but isntead made it match the ID and made the ID match the naming conventions of other ROSA modules.

[kalexand-rh]

/ok-to-test

[openshift-ci]

@jc-berger: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/validate-asciidoc	72ba3ea	link	true	/test validate-asciidoc
ci/prow/validate-portal	72ba3ea	link	true	/test validate-portal

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[jc-berger]

Hi please see this PR which includes the doc preview link: #104758