Remove deprecated file server.pp

REFERENCE.md

@@ -8,7 +8,6 @@
 _Public Classes_
 
 * [`rabbitmq`](#rabbitmq): A module to manage RabbitMQ
-* [`rabbitmq::server`](#rabbitmqserver): Backwards compatibility layer to support including `rabbitmq::server` directly.
 
 _Private Classes_
 
@@ -944,145 +943,6 @@ Data type: `Boolean`
 
 Default value: `false`
 
-### rabbitmq::server
-
-This module manages the installation and config of the rabbitmq server. It is used as backward compability layer for modules which
-  require rabbitmq::server instead of rabbitmq class.
-
-#### Parameters
-
-The following parameters are available in the `rabbitmq::server` class.
-
-##### `port`
-
-Data type: `Integer`
-
-Port that rabbitmq server should listen to
-
-Default value: $rabbitmq::port
-
-##### `delete_guest_user`
-
-Data type: `Boolean`
-
-Whether or not to delete the default user
-
-Default value: $rabbitmq::delete_guest_user
-
-##### `package_name`
-
-Data type: `Variant[String, Array]`
-
-Name of rabbitmq package
-
-Default value: $rabbitmq::package_name
-
-##### `service_name`
-
-Data type: `String`
-
-Name of rabbitmq service
-
-Default value: $rabbitmq::service_name
-
-##### `service_ensure`
-
-Data type: `Enum['running', 'stopped']`
-
-Desired ensure state for service
-
-Default value: $rabbitmq::service_ensure
-
-##### `service_manage`
-
-Data type: `Boolean`
-
-Determines if the service is managed
-
-Default value: $rabbitmq::service_manage
-
-##### `config_stomp`
-
-Data type: `Boolean`
-
-Enable or disable stomp
-
-Default value: $rabbitmq::config_stomp
-
-##### `stomp_port`
-
-Data type: `Integer[1, 65535]`
-
-Port stomp should be listening on
-
-Default value: $rabbitmq::stomp_port
-
-##### `node_ip_address`
-
-Data type: `Optional[String]`
-
-IP address for rabbitmq to bind to
-
-Default value: $rabbitmq::node_ip_address
-
-##### `config`
-
-Data type: `String`
-
-Contents of config file
-
-Default value: $rabbitmq::config
-
-##### `env_config`
-
-Data type: `String`
-
-Contents of env-config file
-
-Default value: $rabbitmq::env_config
-
-##### `config_cluster`
-
-Data type: `Boolean`
-
-Whether to configure a RabbitMQ cluster
-
-Default value: $rabbitmq::config_cluster
-
-##### `cluster_nodes`
-
-Data type: `Array`
-
-Which nodes to cluster with (including the current one)
-
-Default value: $rabbitmq::cluster_nodes
-
-##### `cluster_node_type`
-
-Data type: `Enum['ram', 'disk', 'disc']`
-
-Type of cluster node (disc/disk or ram)
-
-Default value: $rabbitmq::cluster_node_type
-
-##### `erlang_cookie`
-
-Data type: `Optional[String]`
-
-Erlang cookie, must be the same for all nodes in a cluster
-
-Default value: $rabbitmq::erlang_cookie
-
-##### `wipe_db_on_cookie_change`
-
-Data type: `Boolean`
-
-Whether to wipe the RabbitMQ data if the specified erlang_cookie differs from the current one. This is a sad parameter: actually, if
-the cookie indeed differs, then wiping the database is the *only* thing you can do.  You're only required to set this parameter to
-true as a sign that you realise this.
-
-Default value: $rabbitmq::wipe_db_on_cookie_change
-
 ## Resource types
 
 ### rabbitmq_binding