Enforce markdownlint rules MD022,MD031,MD032

- MD022/blanks-around-headings Headings should be surrounded by blank lines
- MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines
- MD032/blanks-around-lists Lists should be surrounded by blank lines

Run the tool locally with the `--fix` argument to autofix the Markdown.

https://github.com/DavidAnson/markdownlint?tab=readme-ov-file#rules--aliases

Author: jbampton

.github/linters/.markdown-lint.yml

@@ -36,9 +36,6 @@ MD013: false
 # MD014/commands-show-output Dollar signs used before commands without showing output
 MD014: false
 
-# MD022/blanks-around-headings Headings should be surrounded by blank lines
-MD022: false
-
 # MD023/heading-start-left Headings must start at the beginning of the line
 MD023: false
 
@@ -57,12 +54,6 @@ MD028: false
 # MD029/ol-prefix Ordered list item prefix
 MD029: false
 
-# MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines
-MD031: false
-
-# MD032/blanks-around-lists Lists should be surrounded by blank lines
-MD032: false
-
 # MD033/no-inline-html Inline HTML
 MD033: false
 

CHANGES.md

@@ -648,6 +648,7 @@ Release notes contain the list of [bug fixes](http://cloudstack.apache.org/docs/
 
 Version 4.2.0
 -------------
+
 Released on October 1 2013.
 Release notes contain the list of [bug fixes](http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Release_Notes/index.html)
 
@@ -662,6 +663,7 @@ Build Tool Changes:
  * The project now uses Maven 3 exclusively to build.
 
 New Features:
+
 * CLOUDSTACK-101: OVS support in KVM
 * CLOUDSTACK-132: Mash up marvin into an interactive auto-completing API shell for CloudStack
 * CLOUDSTACK-241: AWS Style Regions

CONTRIBUTING.md

@@ -3,6 +3,7 @@ Contributing to Apache CloudStack (ACS)
 
 Summary
 -------
+
 This document covers how to contribute to the ACS project. ACS uses GitHub PRs to manage code contributions.
 These instructions assume you have a GitHub.com account, so if you don't have one you will have to create one. Your proposed code changes will be published to your own fork of the ACS project, and you will submit a Pull Request for your changes to be added.
 
@@ -26,6 +27,7 @@ No back porting / cherry-picking features to existing branches!
 
 PendingReleaseNotes file
 ------------------------
+
 When developing a new feature or making a (major) change to an existing feature you are encouraged to append this to the PendingReleaseNotes file so that the Release Manager can
 use this file as a source of information when compiling the Release Notes for a new release.
 
@@ -131,4 +133,5 @@ $ git push origin :feature_x
 
 Release Principles
 ------------------
+
 Detailed information about ACS release principles is available at https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+principles+for+Apache+CloudStack+4.6+and+up

README.md

@@ -106,6 +106,7 @@ several communications channels, the [mailing lists](http://cloudstack.apache.or
 official channels for making decisions about the project itself.
 
 Mailing lists:
+
 - [Development Mailing List](mailto:dev-subscribe@cloudstack.apache.org)
 - [Users Mailing List](mailto:users-subscribe@cloudstack.apache.org)
 - [Commits Mailing List](mailto:commits-subscribe@cloudstack.apache.org)

packaging/README.md

@@ -1,26 +1,31 @@
 # CloudStack RPM and DEB packaging
+
 This directory contains all the required scripts and tools needed to build RPM and DEB packages for Apache CloudStack.
 
 These scripts are also used by the CloudStack team to build packages for the official release of CloudStack.
 
 # Requirements
+
 The RPM and DEB packages have dependencies on versions of specific libraries. Due to these dependencies the following distributions and their versions are supported by the packages.
 
 * CentOS / RHEL: 8 and 9
 * Ubuntu: 20.04, 22.04, 24.04
 * Debian 12 (Bookworm, untested!)
 
 # Building
+
 Using the scripts in the *packaging* directory the RPM and DEB packages can be build.
 
 ## DEB
+
 If you simply want to build packages go to the root directory of your CloudStack source code and run:
 
 ``dpkg-buildpackage``
 
 This will build packages for the current distribution version you are running. If you run this on a Ubuntu 16.04 system the packages will be tailored for Ubuntu 16.04 and will not install on Ubuntu 14.04.
 
 ### Building cross-distribution
+
 If you want to build packages for a different distribution run the *build-deb.sh* script. This will build packages with the current distribution as a suffix to the package names. E.g. *cloudstack-agent_4.9.0~xenial_all.deb*
 
 Using a Docker image you can build packages for a distribution you are not running.
@@ -36,6 +41,7 @@ The following commands assume that the CloudStack source is present in **/tmp/cl
 The commands above will generate Ubuntu 14.04, 16.04, and 22.04 packages which you will find in */tmp* on your system after the build succeeds.
 
 ## RPM
+
 The *package.sh* script can be used to build RPM packages for CloudStack. In the *packaging* script you can run the following command:
 
 ``./package.sh --pack oss --distribution el8``

plugins/storage/volume/adaptive/README.md

@@ -11,6 +11,7 @@ and implement the ProviderAdapter without needing to understand the internal
 logic of volume management, database structure, etc.
 
 ## Implement the Provider Interface
+
 To implement a provider, create another module -- or a standalone project --
 and implement the following interfaces from the **org.apache.cloudstack.storage.datastore.adapter** package:
 
@@ -20,21 +21,28 @@ and implement the following interfaces from the **org.apache.cloudstack.storage.
 Follow Javadoc for each class on further instructions for implementing each function.
 
 ## Implement the Primary Datastore Provider Plugin
+
 Once the provider interface is implemented, you will need to extend the **org.apache.cloudstack.storage.datastore.provider.AdaptiveProviderDatastoreProviderImpl** class.  When extending it, you simply need to implement a default
 constructor that creates an instance of the ProviderAdapterFactory implementation created in #2 above.  Once created, you need to call the parent constructor and pass the factory object.
 
 ## Provide the Configuration for the Provider Plugin
+
 Lastly, you need to include a module file and Spring configuration for your Primary Datastore Provider Plugin class so Cloudstack will load it during startup.
 
 ### Module Properties
+
 This provides the hint to Cloudstack to load this as a module during startup.
+
 ```
 #resources/META-INF/cloudstack/storage-volume-<providername>/module.properties
 name=storage-volume-<providername>
 parent=storage
 ```
+
 ### Spring Bean Context Configuration
+
 This provides instructions of which provider implementation class to load when the Spring bean initialization is running.
+
 ```
 <!-- resources/META-INF/cloudstack/storage-volume-<providername>/spring-storage-volume-<providername>-context.xml -->
 <beans xmlns="http://www.springframework.org/schema/beans"
@@ -53,12 +61,16 @@ This provides instructions of which provider implementation class to load when t
 	  </bean>
 </beans>
 ```
+
 ## Build and Deploy the Jar
+
 Once you build the new jar, start Cloudstack Management Server or, if a standalone jar, add it to the classpath before start.  You should now have a new storage provider of the designated name once Cloudstack finishes loading
 all configured modules.
 
 ### Test Cases
+
 The following test cases should be run against configured installations of each storage array in a working Cloudstack installation.
+
 1. Create New Primera Storage Pool for Zone
 2. Create New Primera Storage Pool for Cluster
 3. Update Primera Storage Pool for Zone

plugins/storage/volume/linstor/CHANGELOG.md

@@ -20,6 +20,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [2025-05-07]
 
 ### Added
+
 - Implemented storage/volume stats
 
 ## [2025-03-13]
@@ -49,6 +50,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [2024-12-19]
 
 ### Added
+
 - Native CloudStack encryption support
 
 ## [2024-12-13]

plugins/storage/volume/storpool/README.md

@@ -7,6 +7,7 @@
 Primary storage is associated with a cluster or zone, and it stores the virtual disks for all the VMs running on hosts in that cluster/zone.
 
 Secondary storage stores the following:
+
 * Templates — OS images that can be used to boot VMs and can include additional configuration information, such as installed applications
 * ISO images — disc images containing data or bootable media for operating systems
 * Disk volume snapshots — saved copies of VM data which can be used for data recovery or to create new templates
@@ -354,6 +355,7 @@ To change the tier via CloudStack, you can use the CloudStack API call `changeOf
 	change offeringforvolume id={The UUID of the Volume} diskofferingid={The UUID of the disk offering} size={The current or a new size for the volume}
 
 Users who were using the offerings to change the StorPool template via the `SP_TEMPLATE` detail, will continue to have this functionality but should use `changeOfferingForVolume` API call instead of:
+
  - `resizeVolume` API call for DATA disk
  - `scaleVirtualMachine` API call for ROOT disk
 
@@ -372,9 +374,11 @@ Add disk offering detail with API call in CloudStack CLI.
 Creating VM with QoS
 
 Deploy virtual machine: Go to Compute> Instances> Add Instances.
+
  - For the ROOT volume, choose the option `Override disk offering`. This will set the required `qc` tag from the disk offering (DO) detail.
 
 Creating DATA disk with QoS
+
  - Create volume via GUI/CLI and choose a disk offering which has the required `SP_QOSCLASS` detail
 
 To update the tier of a ROOT/DATA volume go to Storage> Volumes and select the Volume and click on the Change disk offering for the volume in the upper right corner.

test/integration/plugins/linstor/README.md

@@ -1,8 +1,10 @@
 # Linstor storage plugin
+
 ==================================
 This directory contains the basic VM, Volume life cycle tests for Linstor storage pool (in KVM hypervisor).
 
 # Running tests
+
 ===============
 To run the basic volume tests, first update the below test data of the CloudStack environment
 

test/integration/plugins/scaleio/README.md

@@ -1,8 +1,10 @@
 # PowerFlex/ScaleIO storage plugin
+
 ==================================
 This directory contains the basic VM, Volume life cycle tests for PowerFlex/ScaleIO storage pool (in KVM hypervisor).
 
 # Running tests
+
 ===============
 To run the basic volume tests, first update the below test data of the CloudStack environment