-
Story
-
Resolution: Unresolved
-
Normal
-
rhos-18.0.z
-
None
-
5
-
False
-
-
False
-
rhos-ops-day1day2-upgrades
-
-
Goal:
- As a writer, I want to reformat the code blocks in the adoption guide to ensure that they copy properly when a customer uses the copy button.
- This story covers the steps that combine the oc patch command with file contents. The copy button only copies the command in this case. I need to split the step into something like this:
- Create a new file, for example, ceph_backend.patch, and include the following content:
spec:
{{ extraMounts:}}
{{ - name: v1}}Unknown macro: {{…}}
- Patch the OpenStackControlPlane CR to inject ceph.conf and ceph.client.openstack.keyring to the RHOSP services that are defined in the propagation list:
$ oc patch openstackcontrolplane openstack --type=merge --patch-file=ceph_backend.patch
- Create a new file, for example, ceph_backend.patch, and include the following content:
- This story covers the steps that combine the oc patch command with file contents. The copy button only copies the command in this case. I need to split the step into something like this:
Acceptance Criteria:
- Apply the guidelines from: https://docs.google.com/document/d/1A9jTYULe7r1IH3IV5kgQTq3ZGLuSceVnMVG4SBto6jE/edit?tab=t.0#heading=h.3mtk691wxx68
- New guidelines in style guide: https://redhat-documentation.github.io/supplementary-style-guide/#commands-in-code-blocks
- My own tracking Gdoc: https://docs.google.com/document/d/1LF9lMBnheWX9xe8v2ojbybEkHEuNqqQEDJLsCAjITog/edit?tab=t.0