Version information
This version is compatible with:
- Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2016.4.x
- Puppet >= 4.10.0 < 7.0.0
Start using this module
Add this module to your Puppetfile:
mod 'brwyatt-vim', '0.1.2'
Learn more about managing modules with a PuppetfileDocumentation
vim
Install vim and manage user configuration files
Table of Contents
- Description
- Setup - The basics of getting started with vim
- Usage - Configuration options and additional functionality
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
Description
This module installs vim and manages vim user configuration files. Currently, this module allows managing of user .vimrc
, vim plugins, and Pathogen bundles.
Setup
What vim affects
When this module is used to manage a user's vim config, it will manage the entire .vim
directory for that user, and remove unmannaged files.
Setup Requirements
This module currently only officially supports Ubuntu, but likely will work on most other systems, particularly of a Debian flavor. If using on non-Debian based distros, it may be necessary to manually provide the vim package name. Additionally, only Git-based repos are officially supported. Others may work, but only Git has been tested.
This module additionally has the following dependencies:
lwf/remote_file
: used whenVim::Plugin
is provided an http/https URL for thesource
parameter.puppetlabs/git
: used to install Pathogen bundles from git (if using a Git repo)puppetlabs/stdlib
: defaultpuppetlabs/vcsrepo
: used for installing/managing Pathogen bundles. Might be able to support other repo types, but only Git has been tested.
Beginning with vim
Install the module with:
puppet module install brwyatt-vim
Usage
Install vim
To install vim, include the module into your manifests:
include ::vim
All Vim
module resources are realized in Vim::Configure
, so may be included as virtual resources in global user configs, and will only be realized on systems that also include the main Vim
class or Vim::Configure
.
Managing user config
@vim::config { '/home/brwyatt':
ensure => present,
owner => 'brwyatt',
}
This will manage the user's .vimrc
and setup the user's .vim
directory, including directories for plugins and bundles.
Installing plugins
@vim::plugin { 'pathogen':
owner => 'brwyatt',
autoload => true,
source =>
'https://raw.githubusercontent.com/tpope/vim-pathogen/v2.4/autoload/pathogen.vim',
vim_dir => '/home/brwyatt/.vim',
}
This installs the plugin at the indicated source to the user's .vim/plugins
directory, and adds a symlink in .vim/autoload
to it. The file will be called pathogen.vim
and is based on this resource's name, and can be overridden by the plugin_name
parameter.
Installing bundles
@vim::bundle { 'puppet':
ensure => present,
owner => 'brwyatt',
repo => 'https://github.com/voxpupuli/vim-puppet.git',
revision => 'master',
vim_dir => '/home/brwyatt/.vim',
}
This will install the bundle from the indicated Git repository into the user's .vim/bundle
directory as "puppet", based on the resource's name. This name can be overridden with the bundle_name
parameter.
Limitations
Currently, this module can only install on Debian-based systems and has not been tested on distributions other than Ubuntu 16.04 and 18.04. It may or may not work on other Debian-based distributions, but makes no claims regarding such.
Development
Feel free to file issues in the GitHub issue tracker for the repository, or submit Pull Requests.
I may not have much time to work on (or test) this myself, so help to expand current functionality (especially to make it work for more people) is greatly appreciated and encouraged.
Contributors
The list of contributors can be found at: https://github.com/brwyatt/puppet-vim/graphs/contributors.
Reference
Table of Contents
Classes
vim
: Installs and configures the vim package.vim::configure
: Global vim configuration. Realizes all virtual user configs and sets up resource order. It is not recommended to include this directly.vim::install
: Installs the vim package. It is not recommended to use this class directly.
Defined types
vim::bundle
: Install Pathogen/vim plugin bundles.vim::config
: Manage a user's vim configuration.vim::plugin
: Install a vim pugin.
Classes
vim
Installs and configures the vim package.
Examples
include vim
vim::configure
Global vim configuration. Realizes all virtual user configs and sets up resource order. It is not recommended to include this directly.
Examples
include vim::configure
vim::install
Installs the vim package. It is not recommended to use this class directly.
Examples
include vim::install
Parameters
The following parameters are available in the vim::install
class.
package_ensure
Data type: String
Ensure to pass to the package resource.
package_name
Data type: String
Vim package name for the package resource.
Defined types
vim::bundle
Install Pathogen/vim plugin bundles.
Examples
Install Puppet bundle from GitHub
vim::bundle { 'puppet':
ensure => present,
owner => 'brwyatt',
repo => 'https://github.com/voxpupuli/vim-puppet.git',
revision => 'master',
vim_dir => '/home/brwyatt/.vim',
}
Parameters
The following parameters are available in the vim::bundle
defined type.
owner
Data type: String
The username of the owner of this bundle's files.
repo
Data type: String
URL/Path to the repo source for the bundle.
vim_dir
Data type: String
Path to the user's .vim
directory containing the bundles
directory.
bundle_name
Data type: String
The bundle's name.
Default value: $name
ensure
Data type: Enum['present', 'absent']
Resource ensure value.
Default value: 'present'
group
Data type: String
Group name for bundle's permissions.
Default value: $owner
provider
Data type: String
The provider value to pass to vcsrepo
. Can be any valid provider accepted by vcsrepo
.
Default value: 'git'
revision
Data type: String
Repository revision to checkout.
Default value: 'master'
vim::config
Manage a user's vim configuration.
Examples
vim::config { '/home/brwyatt':
ensure => present,
owner => 'brwyatt',
}
Parameters
The following parameters are available in the vim::config
defined type.
owner
Data type: String
Username of the owner of the configs.
vimrc_template
Data type: String
Template file/path used to generate the user's .vimrc
.
Default value: 'vim/pathogen_vimrc.epp'
vimrc_params
Data type: Hash
Template params to pass to the template indicated by $vimrc_template
.
Default value: {}
ensure
Data type: Enum['present', 'absent']
Resource ensure.
Default value: 'present'
group
Data type: String
Name of the group that owns the configs.
Default value: $owner
path
Data type: String
The path to the directory containing the configs. This should be the parent directory that the .vimrc
and .vim
directory should be created.
Default value: $name
vim::plugin
Install a vim pugin.
Examples
vim::plugin { 'pathogen':
owner => 'brwyatt',
autoload => true,
source =>
'https://raw.githubusercontent.com/tpope/vim-pathogen/v2.4/autoload/pathogen.vim',
vim_dir => '/home/brwyatt/.vim',
}
Parameters
The following parameters are available in the vim::plugin
defined type.
owner
Data type: String
The username of the owner of this plugin.
vim_dir
Data type: String
Path to the user's .vim
directory containing the plugin
and autoload
directories.
autoload
Data type: Boolean
Controls if this plugin should be symlinked from the autoload
directory.
Default value: false
plugin_name
Data type: String
The plugin's name. .vim
will be appended to this name if not included.
Default value: $name
ensure
Data type: Enum['present', 'absent']
Resource ensure value.
Default value: 'present'
group
Data type: String
Group name for plugin's permissions.
Default value: $owner
content
Data type: Optional[String]
Content of the plugin file. Mutually exclusive with $source
.
Default value: undef
source
Data type: Optional[String]
Source location of the plugin file. Mutually exclusive with $content
.
Note: if source is an http/https URL, $content
is ignored completely without error.
Default value: undef
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning
0.1.2 - 2019-05-24
Added
- PDK Update
- Add Forge credentials to Travis config
- Fix style guide errors
0.1.1 - 2018-12-23
Added
- License file
0.1.0 - 2018-12-23
Initial release
Dependencies
- lwf/remote_file (>= 1.1.0 < 1.2.0)
- puppetlabs/git (>= 0.5.0 < 0.6.0)
- puppetlabs/stdlib (>= 4.25.0 < 4.26.0)
- puppetlabs/vcsrepo (>= 2.4.0 < 3.0.0)
GNU LESSER GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below. 0. Additional Definitions. As used herein, "this License" refers to version 3 of the GNU Lesser General Public License, and the "GNU GPL" refers to version 3 of the GNU General Public License. "The Library" refers to a covered work governed by this License, other than an Application or a Combined Work as defined below. An "Application" is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library. A "Combined Work" is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the "Linked Version". The "Minimal Corresponding Source" for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version. The "Corresponding Application Code" for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work. 1. Exception to Section 3 of the GNU GPL. You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL. 2. Conveying Modified Versions. If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version: a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy. 3. Object Code Incorporating Material from Library Header Files. The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following: a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License. b) Accompany the object code with a copy of the GNU GPL and this license document. 4. Combined Works. You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following: a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License. b) Accompany the Combined Work with a copy of the GNU GPL and this license document. c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document. d) Do one of the following: 0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source. 1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version. e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.) 5. Combined Libraries. You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following: a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License. b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work. 6. Revised Versions of the GNU Lesser General Public License. The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation. If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.