Merge pull request #312 from miharp/docs/issue-274-kramdown-ial

docs: remove legacy Kramdown topic-type IAL markers (openvox 8.x)

Author: tuxmea

docs/_openvox_8x/cheatsheet_core_types.md

@@ -20,7 +20,6 @@ Related topics:
 
 * [Type reference](./type.html)
 
-{:.concept}
 ## The Trifecta
 
 Package/file/service: Learn it, live it, love it. Even if this is the only Puppet you know, you can still get a whole lot done.
@@ -47,12 +46,10 @@ service { 'sshd':
 
 <!--**INSERT PICTURE OF DEPENDENCY GRAPH HERE**-->
 
-{:.concept}
 ### file
 
 Manages files, directories, and symlinks.
 
-{:.section}
 #### Important Attributes
 
 * [`ensure`](./type.html#file-attribute-ensure) -- Whether the file should exist, and what it should be. Allowed values:
@@ -66,25 +63,21 @@ Manages files, directories, and symlinks.
 * [`group`](./type.html#file-attribute-group) -- By name or GID.
 * [`mode`](./type.html#file-attribute-mode) -- Must be specified exactly. Does the right thing for directories.
 
-{:.section}
 #### For Normal Files
 
 * [`source`](./type.html#file-attribute-source) -- Where to download contents for the file. Usually a `puppet:///` URL.
 * [`content`](./type.html#file-attribute-content) -- The file's desired contents, as a string. Most useful when paired with [templates](./lang_template.html), but you can also use the output of the [file function](./function.html#file).
 
-{:.section}
 #### For Directories
 
 * [`source`](./type.html#file-attribute-source) -- Where to download contents for the directory, when `recurse => true`.
 * [`recurse`](./type.html#file-attribute-recurse) -- Whether to recursively manage files in the directory.
 * [`purge`](./type.html#file-attribute-purge) -- Whether unmanaged files in the directory should be deleted, when `recurse => true`.
 
-{:.section}
 #### For Symlinks
 
 * [`target`](./type.html#file-attribute-target) -- The symlink target. (Required when `ensure => link`.)
 
-{:.section}
 #### Other Notable Attributes
 
 * [`backup`](./type.html#file-attribute-backup)
@@ -95,12 +88,10 @@ Manages files, directories, and symlinks.
 * [`recurselimit`](./type.html#file-attribute-recurselimit)
 * [`replace`](./type.html#file-attribute-replace)
 
-{:.concept}
 ### package
 
 Manages software packages.
 
-{:.section}
 #### Important Attributes
 
 * [`name`](./type.html#package-attribute-name) -- The name of the package, as known to your packaging system; **defaults to title.**
@@ -113,7 +104,6 @@ Manages software packages.
 * [`source`](./type.html#package-attribute-source) -- Where to obtain the package, if your system's packaging tools don't use a repository.
 * [`provider`](./type.html#package-attribute-provider) -- Which packaging system to use (e.g. Yum vs. Rubygems), if a system has more than one available.
 
-{:.concept}
 ### service
 
 Manages services running on the node. Like with packages, some platforms have better tools than others, so read up.
@@ -124,7 +114,6 @@ Related topics:
 
 * [Relationships](./lang_relationships.html)
 
-{:.section}
 #### Important Attributes
 
 * [`name`](./type.html#service-attribute-name) -- The name of the service to run; **defaults to title.**
@@ -135,16 +124,13 @@ Related topics:
 * [`hasrestart`](./type.html#service-attribute-hasrestart) -- Whether to use the init script's restart command instead of stop+start. Defaults to false.
 * [`hasstatus`](./type.html#service-attribute-hasstatus) -- Whether to use the init script's status command. Defaults to true.
 
-{:.section}
 #### Other Notable Attributes
 
 If a service has a bad init script, you can work around it and manage almost anything using the [`status`](./type.html#service-attribute-status), [`start`](./type.html#service-attribute-start), [`stop`](./type.html#service-attribute-stop), [`restart`](./type.html#service-attribute-restart), [`pattern`](./type.html#service-attribute-pattern), and [`binary`](./type.html#service-attribute-binary) attributes.
 
 
-{:.concept}
 ## Hello World
 
-{:.concept}
 ### notify
 
 Logs an arbitrary message, at the `notice` log level. This appears in the POSIX syslog or Windows Event Log on the OpenVox agent node and is also logged in reports.
@@ -153,41 +139,34 @@ Logs an arbitrary message, at the `notice` log level. This appears in the POSIX
 notify { 'This message is getting logged on the agent node.': }
 ```
 
-{:.section}
 #### Important Attributes
 
 * [`message`](./type.html#notify-attribute-message) -- **Defaults to title.**
 
-{:.concept}
 ## Grab bag
 
-{:.concept}
 ### [exec][]
 
 Executes an arbitrary command on the agent node. When using execs, you must either make sure the command can be safely run multiple times, or specify that it should only run under certain conditions.
 
-{:.section}
 #### Important Attributes
 
 * [`command`](./type.html#exec-attribute-command) -- The command to run; **defaults to title.** If this isn't a fully-qualified path, use the `path` attribute.
 * [`path`](./type.html#exec-attribute-path) -- Where to look for executables, as a colon-separated list or an array.
 * [`returns`](./type.html#exec-attribute-returns) -- Which exit codes indicate success. Defaults to `0`.
 * [`environment`](./type.html#exec-attribute-environment) -- An array of environment variables to set (for example, `['MYVAR=somevalue', 'OTHERVAR=othervalue']`).
 
-{:.section}
 #### Attributes to Limit When a Command Should Run
 
 * [`creates`](./type.html#exec-attribute-creates) -- A file to look for before running the command. The command only runs if the file doesn’t exist.
 * [`refreshonly`](./type.html#exec-attribute-refreshonly) -- If `true`, the command only run if a resource it subscribes to (or a resource which notifies it) has changed.
 * [`onlyif`](./type.html#exec-attribute-onlyif) -- A command or array of commands; if any have a non-zero return value, the command won't run.
 * [`unless`](./type.html#exec-attribute-unless) -- The opposite of onlyif.
 
-{:.section}
 #### Other Notable Attributes:
 
 [`cwd`](./type.html#exec-attribute-cwd), [`group`](./type.html#exec-attribute-group), [`logoutput`](./type.html#exec-attribute-logoutput), , [`timeout`](./type.html#exec-attribute-timeout), [`tries`](./type.html#exec-attribute-tries), [`try_sleep`](./type.html#exec-attribute-try_sleep), [`user`](./type.html#exec-attribute-user).
 
-{:.concept}
 ### [user][]
 
 Manages user accounts; mostly used for system users.
@@ -201,7 +180,6 @@ Manages user accounts; mostly used for system users.
         managehome => true,
     }
 
-{:.section}
 #### Important Attributes
 
 * [`name`](./type.html#user-attribute-name) -- The name of the user; **defaults to title.**
@@ -216,17 +194,14 @@ Manages user accounts; mostly used for system users.
 * [`managehome`](./type.html#user-attribute-managehome) -- Whether to manage the home directory when managing the user; if you don't set this to true, you'll need to create the user's home directory manually.
 * [`shell`](./type.html#user-attribute-shell) -- The user's login shell.
 
-{:.section}
 #### Other Notable Attributes
 
 [`comment`](./type.html#user-attribute-comment), [`expiry`](./type.html#user-attribute-expiry), [`membership`](./type.html#user-attribute-membership), [`password`](./type.html#user-attribute-password), [`password_max_age`](./type.html#user-attribute-password_max_age), [`password_min_age`](./type.html#user-attribute-password_min_age), [`purge_ssh_keys`](./type.html#user-attribute-purge_ssh_keys), [`salt`](./type.html#user-attribute-salt).
 
-{:.concept}
 ### [group][]
 
 Manages groups.
 
-{:.section}
 #### Important Attributes
 
 * [`name`](./type.html#group-attribute-name) -- The name of the group; **defaults to title.**

docs/_openvox_8x/cheatsheet_module.md

@@ -12,7 +12,6 @@ title: Module cheat sheet
 [forge]: https://forge.puppet.com/
 [documentation]: ./modules_documentation.html
 
-{:.reference}
 ## Module cheat sheet
 
 A quick reference to Puppet module terms and concepts.
@@ -29,7 +28,6 @@ Related topics:
 
 **Example Module: `/etc/puppetlabs/puppet/modules/apache`**
 
-{:.section}
 ### manifests
 
 This directory holds the module's Puppet code.
@@ -73,7 +71,6 @@ class apache::config::ssl {
 
 Subdirectories add intermediate namespaces.
 
-{:.section}
 ### files
 
 Nodes can download any files in this directory from Puppet's built-in file server.
@@ -106,7 +103,6 @@ file { '/etc/apache2/httpd-ssl.conf':
 }
 ```
 
-{:.section}
 ### lib
 
 This directory holds Ruby plugins, which can add features to Puppet and Facter.
@@ -120,7 +116,6 @@ A custom function.
 apache/lib/facter/apache_confdir.rb**
 A custom fact.
 
-{:.section}
 ### templates
 
 This directory holds ERB templates.

docs/_openvox_8x/config_about_settings.markdown

@@ -19,7 +19,6 @@ See also:
 
 Settings can be set in the main config file. Puppet's main config file is called `puppet.conf`.
 
-{:.concept}
 ## Main settings and extra config files
 
 When we mention "settings" in the context of Puppet, we usually mean the main settings. These are the settings that are listed in the configuration reference. They are valid in `puppet.conf` and available for use on the command line. These settings configure nearly all of Puppet's core features.
@@ -29,21 +28,18 @@ However, there are also about nine extra configuration files --- things like `au
 -   The main settings only support a few types of values. Some things just can't be configured without complex data structures, so they needed separate files. (Authorization rules and custom CSR attributes are in this category.)
 -   Puppet currently doesn't allow extensions to add new settings to `puppet.conf`. This means some settings that _should_ be main settings (like the PuppetDB server) can't be.
 
-{:.section}
 ### Puppet Server configuration
 
 Puppet Server honors almost all settings in `puppet.conf` and should pick them up automatically. However, for some tasks, such as configuring the webserver or an external Certificate Authority, there are Puppet Server-specific configuration files and settings.
 
 See [Puppet Server: Configuration][puppetserver_config]
 
-{:.concept}
 ## Settings are loaded on startup
 
 When any Puppet command or service starts up, it gets values for all of its settings. Any of these settings could change the way that command or service behaves.
 
 A command or service _only_ reads its settings _once;_ if something needs to be reconfigured, it needs to be restarted or run again.
 
-{:.reference}
 ## Settings on the command line
 
 Settings from the command line have top priority, and **always override settings from the config file.** When a Puppet command or service is started, you can specify any setting as a command line option.
@@ -52,7 +48,6 @@ Settings require two hyphens and the name of the setting on the command line:
 
 `$ sudo puppet agent --test --noop --certname temporary-name.example.com`
 
-{:.reference}
 ## Basic settings
 
 For most settings, you specify the option and follow it with a value. An equals sign between the two (`=`) is optional, and you can optionally put values in quotes.
@@ -65,7 +60,6 @@ All three of these are equivalent to setting `certname = temporary-name.example.
 
 `--certname "temporary-name.example.com"`
 
-{:.reference}
 ## Boolean settings
 
 Settings whose only valid values are `true` and `false`, use a shorter format. Specifying the option alone sets the setting to `true`, or prefixing the option with `no-` sets it to false.
@@ -76,14 +70,12 @@ This means:
 
 `--no-noop` is equivalent to setting `noop = false` in `puppet.conf`.
 
-{:.reference}
 ## Default values
 
 If a setting isn't specified on the command line or in `puppet.conf`, it falls back to a default value. Default values for all settings are listed in the configuration reference.
 
 Some default values are based on other settings --- when this is the case, the default is shown using the other setting as a variable (similar to `$ssldir/certs`).
 
-{:.concept}
 ## Configuring locale settings
 
 Puppet 5.1 added support for locale-specific strings in output, and it detects your locale from your system configuration. This provides localized strings, report messages, and log messages for the locale's language when available.
@@ -92,7 +84,6 @@ Upon startup, Puppet looks for a set of environment variables on \*nix systems,
 
 For help setting your operating system's locale or adding new locales, consult its documentation. This section covers setting the locale for Puppet services.
 
-{:.task}
 ### Checking your locale settings on \*nix and macOS
 
 To check your current locale settings, run the `locale` command. This outputs the settings used by your current shell.
@@ -117,7 +108,6 @@ To check the current status of environment variables that might conflict with or
 sudo set | egrep 'LANG|LC_'
 ```
 
-{:.task}
 ### Checking your locale settings on Windows
 
 To check your current locale setting, run the `Get-WinSystemLocale` command from PowerShell.
@@ -131,7 +121,6 @@ LCID             Name             DisplayName
 
 To check your system's current code page setting, run the `chcp` command.
 
-{:.task}
 ### Setting your locale on *nix with an environment variable
 
 You can use environment variables to set your locale for processes started on the command line. For most Linux distributions, set the `LANG` variable to your preferred locale, and the `LANGUAGE` variable to an empty string. On SLES, also set the `LC_ALL` variable to an empty string.
@@ -151,7 +140,6 @@ To set the locale for the OpenVox agent service, you can add these `export` stat
 
 After updating the file, restart the Puppet service to apply the change.
 
-{:.task}
 ### Setting your locale for the OpenVox agent service on macOS
 
 To set the locale for the OpenVox agent service on macOS, update the `LANG` setting in the `/Library/LaunchDaemons/com.puppetlabs.puppet.plist` file.
@@ -165,7 +153,6 @@ To set the locale for the OpenVox agent service on macOS, update the `LANG` sett
 
 After updating the file, restart the Puppet service to apply the change.
 
-{:.task}
 ### Setting your locale on Windows
 
 On Windows, Puppet uses the `LANG` environment variable if it is set. If not, it uses the configured region, as set in the Administrator tab of the Region control panel.
@@ -176,7 +163,6 @@ On Windows 10, you can use PowerShell to set the system locale:
 Set-WinSystemLocale en-US
 ```
 
-{:.task}
 ### Disabling internationalized strings
 
 Puppet 5.3.2 added the optional Boolean `disable_i18n` setting, which you can configure in `puppet.conf`. If set to `true`, Puppet disables localized strings in log messages, reports, and parts of the command-line interface. This can improve performance when using Puppet modules, especially if [environment caching](./configuration.html#environment_timeout) is disabled, and even if you don't need localized strings or the modules aren't localized. This setting is `false` by default in open source Puppet.

docs/_openvox_8x/config_file_auth.markdown

@@ -30,7 +30,6 @@ Access to Puppet's HTTPS API is configured in `auth.conf`.
 >
 > The default location of the new `auth.conf` is `/etc/puppetlabs/puppetserver/conf.d/auth.conf`. See [the Puppet Server `auth.conf` docs][server_auth_conf] for details.
 
-{:.concept}
 ## Puppet's HTTPS API
 
 The OpenVox agent service requests configurations over HTTPS, and the OpenVox Server application provides several HTTPS endpoints to support this. (For example, requesting a catalog uses a different endpoint than submitting a report.) There are also a few endpoints that aren't used by OpenVox agent.

docs/_openvox_8x/dirs_codedir.markdown

@@ -8,7 +8,6 @@ title: "Code and data directory (codedir)"
 
 Puppet's `codedir` is the main directory for Puppet code and data. It contains environments (which contain your manifests and modules), a global modules directory for all environments, and your Hiera data.
 
-{:.concept}
 ## Location
 
 Puppet's codedir can be found at one of the following locations:
@@ -23,12 +22,10 @@ The system codedir is what you usually want to use, since you will usually run P
 
 > **Note:** When OpenVox Server is running as a Rack application, the `config.ru` file must explicitly set `--codedir` to the system codedir. The example `config.ru` file provided with the Puppet source does this.
 
-{:.section}
 ### Configuration
 
 The location of the codedir can be configured in puppet.conf with [the `codedir` setting][codedir], but note that Puppet Server doesn't use that setting; it has its own `jruby-puppet.master-code-dir` setting [in puppetserver.conf][puppetserver_conf]. If you're using a non-default codedir, _you must change both settings._
 
-{:.concept}
 ## Interpolation of `$codedir`
 
 Since the value of the codedir is discovered before other settings, you can safely reference it (with the `$codedir` variable) in the value of any other setting in puppet.conf:
@@ -38,14 +35,12 @@ Since the value of the codedir is discovered before other settings, you can safe
 
 If you need to set nonstandard values for some settings, this allows you to avoid absolute paths and keep your Puppet-related files together.
 
-{:.concept}
 ### Contents
 
 Puppet's codedir contains environments, modules, and Hiera data. Its contents are used by OpenVox Server and Puppet apply, but not by OpenVox agent.
 
 Almost everything in the codedir has its own page of documentation.
 
-{:.section}
 ### Code and Data Directories
 
 * [`environments`](./environments_creating.html) --- contains alternate versions of the `modules` and `manifests` directories, to allow code changes to be tested on smaller sets of nodes before entering production.

docs/_openvox_8x/dirs_confdir.markdown

@@ -7,7 +7,6 @@ title: "Directories: Config directory (confdir)"
 
 Puppet's `confdir` is the main directory for Puppet's configuration. It contains config files and SSL data.
 
-{:.concept}
 ## Location
 
 Puppet's confdir can be found at one of the following locations:
@@ -24,7 +23,6 @@ to use the same confdir as OpenVox agent or OpenVox Server.)
 
 > **Note:** When OpenVox Server is running as a Rack application, the `config.ru` file must explicitly set `--confdir` to the system confdir. The example `config.ru` file provided with the Puppet source does this.
 
-{:.section}
 ### Configuration
 
 Puppet's confdir can be specified on the command line with the `--confdir` option, but it can't be set
@@ -36,14 +34,12 @@ to configure its confdir. Note that if you're using a non-default confdir, you m
 `--confdir` whenever you run commands like `puppet module` to ensure they use the same directories as
 Puppet Server.
 
-{:.concept}
 ## Interpolation of `$confdir`
 
 Since the value of the confdir is discovered before other settings, you can safely reference it (with the `$confdir` variable) in the value of any other setting in puppet.conf.
 
 If you need to set nonstandard values for some settings, this allows you to avoid absolute paths and keep your Puppet-related files together.
 
-{:.concept}
 ## Contents
 
 Puppet's confdir contains several config files and the SSL data. Their locations can be changed with settings, but most users should use the default layout.
@@ -52,12 +48,10 @@ Almost everything in the confdir has its own page of documentation.
 
 Items labeled "master only" below can also be present on standalone Puppet apply nodes, since they act as both masters and agents.
 
-{:.section}
 ### SSL Data
 
 * [`ssl`](./dirs_ssldir.html) --- contains each node's certificate infrastructure. (All nodes.)
 
-{:.section}
 ### Config files
 
 * [`puppet.conf`](./config_file_main.html) --- Puppet's main config file. (Any node.)