Skip to content
This repository has been archived by the owner on May 19, 2023. It is now read-only.

Tweaks the callout rules #66

Merged
merged 1 commit into from
May 4, 2023
Merged

Tweaks the callout rules #66

merged 1 commit into from
May 4, 2023

Conversation

aireilly
Copy link
Collaborator

@aireilly aireilly commented May 4, 2023

This tweak adjusts some descriptions and changes how the seq callouts rulwe works. Now, it only fires for non-sequential callouts outside the listing block.

@aireilly
Copy link
Collaborator Author

aireilly commented May 4, 2023

This should not cause an error:

modules/windows-machineset-vsphere.adoc:67
modules/cpmso-creating-cr.adoc:61

<1> Specify the infrastructure ID that is based on the cluster ID that you set when you provisioned the cluster. You must specify this value when you create a `ControlPlaneMachineSet` CR. If you have the OpenShift CLI (`oc`) installed, you can obtain the infrastructure ID by running the following command:
+
[source,terminal]
----
$ oc get -o jsonpath='{.status.infrastructureName}{"\n"}' infrastructure cluster
----
<2> Specify the state of the Operator. When the state is `Inactive`, the Operator is not operational. You can activate the Operator by setting the value to `Active`.

@rohennes
Copy link
Owner

rohennes commented May 4, 2023

LGTM - this passes repeated numbers and numbers out of sequence inside the codeblock (I think!)

@rohennes rohennes merged commit 66570e8 into rohennes:main May 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants