OBSDOCS-3537: Fix incorrect field reference in COO CLI Subscription example#113874
OBSDOCS-3537: Fix incorrect field reference in COO CLI Subscription example#113874kiranrpatil12 wants to merge 1 commit into
Conversation
…xample Change spec.namespace to metadata.namespace in the field description for the Subscription object. A Subscription has no spec.namespace field; the target namespace is set under metadata.namespace. Co-authored-by: Cursor <cursoragent@cursor.com>
openshift-ci-robot
added
the
jira/valid-reference
|
@kiranrpatil12: This pull request references OBSDOCS-3537 which is a valid jira issue. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
Bot
added
the
size/XS
|
🤖 Mon Jun 22 21:20:07 - Prow CI generated the docs preview: |
|
@kiranrpatil12: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
3 participants
Summary
Fixes the incorrect field reference in the "Installing the COO by using the CLI" section.
Bug: The parameter description references
spec.namespace, but a Subscription object does not have that field.Fix: Changed the field description to
metadata.namespace, matching the YAML example above it.Jira
Version(s): 6.6 (main), cherry-pick to 6.5 and 6.4 as needed
Issue: https://redhat.atlassian.net/browse/OBSDOCS-3537
Link to docs preview:
QE review:
Additional information:
The YAML example already correctly uses
metadata.namespace: openshift-operators. Only the field description below the example was wrong.Source file:
modules/installing-the-coo-cli.adoc