gitlab
Contributions Requested
10,847 downloads
10,500 latest version
2.0 quality score
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.
Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.
Support the Puppet Community by contributing to this module
You are welcome to contribute to this module by suggesting new features, currency updates, or fixes. Every contribution is valuable to help ensure that the module remains compatible with the latest Puppet versions and continues to meet community needs. Complete the following steps:
- Review the module’s contribution guidelines and any licenses. Ensure that your planned contribution aligns with the author’s standards and any legal requirements.
- Fork the repository on GitHub, make changes on a branch of your fork, and submit a pull request. The pull request must clearly document your proposed change.
For questions about updating the module, contact the module’s author.
Version information
- 0.0.2 (latest)
- 0.0.1
Start using this module
- r10k or Code Manager
- Bolt
- Manual installation
- Direct download
Add this module to your Puppetfile:
mod 'lboynton-gitlab', '0.0.2'Learn more about managing modules with a PuppetfileAdd this module to your Bolt project:
bolt module add lboynton-gitlabLearn more about using this module with an existing projectManually install this module globally with Puppet module tool:
puppet module install lboynton-gitlab --version 0.0.2Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.
DownloadDocumentation
Types in this module release
Manage RVM Gemsets.
| Parameters | |
|---|---|
ensure | |
name | The name of the gemset to be managed. |
provider | |
ruby_version | The ruby version to use. This should be the fully qualified RVM string.
For example: 'ruby-1.9.2-p290'
For a full list of known strings: |
| Providers | |
|---|---|
gemset | RVM gemset support. |
Ruby Gem support using RVM.
| Parameters | |
|---|---|
ensure | What state the gem should be in. Possible values: present - the gem is installed latest - the gem is installed and is the latest stable version absent - the gem is not installed version - the gem is installed and matches the given version |
name | The name of the Ruby gem. |
provider | |
ruby_version | The ruby version to use. This should be the fully qualified RVM string
(including gemset if applicable). For example: 'ruby-1.9.2-p136@mygemset'
For a full list of known strings: |
source | If a URL is passed via, then that URL is used as the remote gem repository; if a source is present but is not a valid URL, it will be interpreted as the path to a local gem file. If source is not present at all, the gem will be installed from the default gem repositories. |
withopts | Install the gem with these makefile opts. |
| Providers | |
|---|---|
gem | Ruby Gem support using RVM. |
A simple resource type intended to be used as an anchor in a composite class.
In Puppet 2.6, when a class declares another class, the resources in the interior class are not contained by the exterior class. This interacts badly with the pattern of composing complex modules from smaller classes, as it makes it impossible for end users to specify order relationships between the exterior class and other modules.
The anchor type lets you work around this. By sandwiching any interior classes between two no-op resources that are contained by the exterior class, you can ensure that all resources in the module are contained.
class ntp {
# These classes will have the correct order relationship with each
# other. However, without anchors, they won't have any order
# relationship to Class['ntp'].
class { 'ntp::package': }
-> class { 'ntp::config': }
-> class { 'ntp::service': }
# These two resources "anchor" the composed classes within the ntp
# class.
anchor { 'ntp::begin': } -> Class['ntp::package']
Class['ntp::service'] -> anchor { 'ntp::end': }
}
This allows the end user of the ntp module to establish require and before relationships with Class['ntp']:
class { 'ntp': } -> class { 'mcollective': }
class { 'mcollective': } -> class { 'ntp': }
| Parameters | |
|---|---|
name | The name of the anchor resource. |
A local version control repository
| Parameters | |
|---|---|
basic_auth_password | HTTP Basic Auth password |
basic_auth_username | HTTP Basic Auth username |
compression | Compression level |
ensure | |
excludes | Files to be excluded from the repository |
force | Force repository creation, destroying any files on the path in the process. |
fstype | Filesystem type |
group | The group/gid that owns the repository files |
identity | SSH identity file |
module | The repository module to manage |
owner | The user/uid that owns the repository files |
path | Absolute path to repository |
provider | |
remote | The remote repository to track |
source | The source URI for the repository |
user | The user to run for repository operations |
| Properties | |
|---|---|
revision | The revision of the repository |
| Providers | |
|---|---|
bzr | Supports Bazaar repositories |
cvs | Supports CVS repositories/workspaces |
dummy | Dummy default provider |
git | Supports Git repositories |
hg | Supports Mercurial repositories |
svn | Supports Subversion repositories |
Ensures that a given line is contained within a file. The implementation matches the full line, including whitespace at the beginning and end. If the line is not contained in the given file, Puppet will add the line to ensure the desired state. Multiple resources may be declared to manage multiple lines in the same file.
Example:
file_line { 'sudo_rule':
path => '/etc/sudoers',
line => '%sudo ALL=(ALL) ALL',
}
file_line { 'sudo_rule_nopw':
path => '/etc/sudoers',
line => '%sudonopw ALL=(ALL) NOPASSWD: ALL',
}
In this example, Puppet will ensure both of the specified lines are
contained in the file /etc/sudoers.
| Parameters | |
|---|---|
ensure | |
line | The line to be appended to the file located by the path parameter. |
match | An optional regular expression to run against existing lines in the file;\nif a match is found, we replace that line rather than adding a new line. |
name | An arbitrary name used as the identity of the resource. |
path | The file Puppet will ensure contains the line specified by the line parameter. |
provider |
| Providers | |
|---|---|
ruby |
Manage RVM Aliases.
| Parameters | |
|---|---|
ensure | |
name | The name of the alias to be managed. |
provider | |
target_ruby | The ruby version that is the target of our alias. For example: 'ruby-1.9.2-p290' |
| Providers | |
|---|---|
alias | RVM alias support. |
Manage RVM Ruby installations.
| Parameters | |
|---|---|
ensure | |
name | The name of the Ruby to be managed. |
provider |
| Properties | |
|---|---|
default_use | Should this Ruby be the system default for new terminals? |
| Providers | |
|---|---|
rvm | Ruby RVM support. |
2013-04-16 Lee Boynton lee@lboynton.com 0.0.2
- Add optional PostgreSQL support (thanks to charlesrg)
- Update to Gitlab 4.2 (thanks to charlesrg) 2013-02-03 Lee Boynton lee@lboynton.com 0.0.1 Initial release
Dependencies
- stahnma/epel (0.0.3)
- maestrodev/rvm (1.0.x)
- puppetlabs/mysql (0.6.x)
- puppetlabs/vcsrepo (0.1.x)
- puppetlabs/nginx (>0.0.1)