Add Gemfile and puppet 4 checks
In anticipation of puppet 4, start trying to deal with puppet 4 things that can be helpfully predicted by puppet lint plugins. Also fix arrow alignment errors not caught before. Change-Id: Ie4df1a6316f10989af653d74aef5306bb79a8870
This commit is contained in:
parent
89d3945873
commit
257a7d00be
2
.gitignore
vendored
Normal file
2
.gitignore
vendored
Normal file
@ -0,0 +1,2 @@
|
||||
Gemfile.lock
|
||||
.bundled_gems/
|
30
Gemfile
Normal file
30
Gemfile
Normal file
@ -0,0 +1,30 @@
|
||||
source 'https://rubygems.org'
|
||||
|
||||
group :development, :test do
|
||||
gem 'puppetlabs_spec_helper', :require => false
|
||||
|
||||
gem 'metadata-json-lint'
|
||||
# This is nice and all, but let's not worry about it until we've actually
|
||||
# got puppet 4.x sorted
|
||||
# gem 'puppet-lint-param-docs'
|
||||
gem 'puppet-lint-absolute_classname-check'
|
||||
gem 'puppet-lint-absolute_template_path'
|
||||
gem 'puppet-lint-trailing_newline-check'
|
||||
|
||||
# Puppet 4.x related lint checks
|
||||
gem 'puppet-lint-unquoted_string-check'
|
||||
gem 'puppet-lint-empty_string-check'
|
||||
gem 'puppet-lint-leading_zero-check'
|
||||
gem 'puppet-lint-variable_contains_upcase'
|
||||
gem 'puppet-lint-spaceship_operator_without_tag-check'
|
||||
gem 'puppet-lint-undef_in_function-check'
|
||||
|
||||
if puppetversion = ENV['PUPPET_GEM_VERSION']
|
||||
gem 'puppet', puppetversion, :require => false
|
||||
else
|
||||
gem 'puppet', '~> 3.0', :require => false
|
||||
end
|
||||
|
||||
end
|
||||
|
||||
# vim:ft=ruby
|
@ -33,12 +33,12 @@ class kibana (
|
||||
}
|
||||
|
||||
file { '/opt/kibana':
|
||||
ensure => directory,
|
||||
owner => 'kibana',
|
||||
group => 'kibana',
|
||||
mode => '0644',
|
||||
recurse => true,
|
||||
require => User['kibana'],
|
||||
ensure => directory,
|
||||
owner => 'kibana',
|
||||
group => 'kibana',
|
||||
mode => '0644',
|
||||
recurse => true,
|
||||
require => User['kibana'],
|
||||
}
|
||||
|
||||
vcsrepo { '/opt/kibana/kibana':
|
||||
|
Loading…
x
Reference in New Issue
Block a user