Permalink
Browse files

initail version

  • Loading branch information...
BernhardDenner committed Nov 25, 2016
1 parent 2b2d982 commit 8451873c67f29ad0a46bfd4073b17ed376394995
18 Gemfile
@@ -0,0 +1,18 @@
source ENV['GEM_SOURCE'] || 'https://rubygems.org'
puppetversion = ENV.key?('PUPPET_VERSION') ? ENV['PUPPET_VERSION'] : ['>= 3.3']
gem 'metadata-json-lint'
gem 'puppet', puppetversion
gem 'puppetlabs_spec_helper', '>= 1.0.0'
gem 'puppet-lint', '>= 1.0.0'
gem 'facter', '>= 1.7.0'
gem 'rspec-puppet'
# rspec must be v2 for ruby 1.8.7
if RUBY_VERSION >= '1.8.7' && RUBY_VERSION < '1.9'
gem 'rspec', '~> 2.0'
gem 'rake', '~> 10.0'
else
# rubocop requires ruby >= 1.9
gem 'rubocop'
end
@@ -0,0 +1,83 @@
# libelektra
#### Table of Contents
1. [Description](#description)
1. [Setup - The basics of getting started with libelektra](#setup)
* [What libelektra affects](#what-libelektra-affects)
* [Setup requirements](#setup-requirements)
* [Beginning with libelektra](#beginning-with-libelektra)
1. [Usage - Configuration options and additional functionality](#usage)
1. [Reference - An under-the-hood peek at what the module is doing and how](#reference)
1. [Limitations - OS compatibility, etc.](#limitations)
1. [Development - Guide for contributing to the module](#development)
## Description
Start with a one- or two-sentence summary of what the module does and/or what
problem it solves. This is your 30-second elevator pitch for your module.
Consider including OS/Puppet version it works with.
You can give more descriptive information in a second paragraph. This paragraph
should answer the questions: "What does this module *do*?" and "Why would I use
it?" If your module has a range of functionality (installation, configuration,
management, etc.), this is the time to mention it.
## Setup
### What libelektra affects **OPTIONAL**
If it's obvious what your module touches, you can skip this section. For
example, folks can probably figure out that your mysql_instance module affects
their MySQL instances.
If there's more that they should know about, though, this is the place to mention:
* A list of files, packages, services, or operations that the module will alter,
impact, or execute.
* Dependencies that your module automatically installs.
* Warnings or other important notices.
### Setup Requirements **OPTIONAL**
If your module requires anything extra before setting up (pluginsync enabled,
etc.), mention it here.
If your most recent release breaks compatibility or requires particular steps
for upgrading, you might want to include an additional "Upgrading" section
here.
### Beginning with libelektra
The very basic steps needed for a user to get the module up and running. This
can include setup steps, if necessary, or it can be an example of the most
basic use of the module.
## Usage
This section is where you describe how to customize, configure, and do the
fancy stuff with your module here. It's especially helpful if you include usage
examples and code samples for doing things with your module.
## Reference
Here, include a complete list of your module's classes, types, providers,
facts, along with the parameters for each. Users refer to this section (thus
the name "Reference") to find specific details; most users don't read it per
se.
## Limitations
This is where you list OS compatibility, version compatibility, etc. If there
are Known Issues, you might want to include them under their own heading here.
## Development
Since your module is awesome, other users will want to play with it. Let them
know what the ground rules for contributing are.
## Release Notes/Contributors/Etc. **Optional**
If you aren't using changelog, put your release notes here (though you should
consider using changelog). You can also add any additional sections you feel
are necessary or important to include here. Please use the `## ` header.
@@ -0,0 +1,32 @@
require 'puppetlabs_spec_helper/rake_tasks'
require 'puppet-lint/tasks/puppet-lint'
require 'metadata-json-lint/rake_task'
if RUBY_VERSION >= '1.9'
require 'rubocop/rake_task'
RuboCop::RakeTask.new
end
PuppetLint.configuration.send('disable_80chars')
PuppetLint.configuration.relative = true
PuppetLint.configuration.ignore_paths = ['spec/**/*.pp', 'pkg/**/*.pp']
desc 'Validate manifests, templates, and ruby files'
task :validate do
Dir['manifests/**/*.pp'].each do |manifest|
sh "puppet parser validate --noop #{manifest}"
end
Dir['spec/**/*.rb', 'lib/**/*.rb'].each do |ruby_file|
sh "ruby -c #{ruby_file}" unless ruby_file =~ %r{spec/fixtures}
end
Dir['templates/**/*.erb'].each do |template|
sh "erb -P -x -T '-' #{template} | ruby -c"
end
end
desc 'Run metadata_lint, lint, validate, and spec tests.'
task :test do
[:metadata_lint, :lint, :validate, :spec].each do |test|
Rake::Task[test].invoke
end
end
@@ -0,0 +1,12 @@
# The baseline for module testing used by Puppet Labs is that each manifest
# should have a corresponding test manifest that declares that class or defined
# type.
#
# Tests are then run by using puppet apply --noop (to check for compilation
# errors and view a log of events) or by fully applying the test in a virtual
# environment (to compare the resulting system state to the desired state).
#
# Learn more about module testing here:
# https://docs.puppet.com/guides/tests_smoke.html
#
include ::libelektra
@@ -0,0 +1,44 @@
module Puppet
Type.type(:kdbkey).provide :kdb do
desc "kdb through kdb command"
#require 'kdb'
puts "kdb provider"
#commands :kdb => "kdb"
confine :true => false
def create
#puts "kdb create"
self.value=(@resource[:value])
end
def destroy
#puts "kdb destroy"
kdb ["rm", @resource[:name]]
end
def exists?
#puts "kdb exists? #{self.name}"
output = execute([command(:kdb), "get", @resource[:name]],
:failonfail => false)
#puts "output: #{output}, #{output.exitstatus}"
output.exitstatus == 0
end
def value
#puts "getting value"
output = kdb ["get", @resource[:name]]
output[-1] = ''
output
end
def value=(value)
#puts "setting value to #{value}"
kdb(["set", @resource[:name], value])
end
end
end
@@ -0,0 +1,69 @@
module Puppet
Type.type(:kdbkey).provide :libelektra do
desc "kdb through libelektra Ruby API"
require 'kdb'
puts "libelektra provider"
#confine :true => true
#confine :exists => "/etc/debian_version"
confine :true => true
def create
puts "libelektra create"
Kdb.open do |db|
ks = Kdb::KeySet.new
db.get ks, "/"
key = Kdb::Key.new @resource[:name], value: @resource[:value]
ks << key
db.set ks, "/"
end
end
def destroy
puts "libelektra destroy"
Kdb.open do |db|
ks = Kdb::KeySet.new
db.get ks, "/"
ks.delete @resource[:name]
db.set ks, "/"
end
end
def exists?
puts "libelektra exists?"
Kdb.open do |db|
ks = Kdb::KeySet.new
db.get ks, "/"
key = ks.lookup @resource[:name]
return !key.nil?
end
end
def value
puts "getting value"
Kdb.open do |db|
ks = Kdb::KeySet.new
db.get ks, "/"
key = ks.lookup @resource[:name]
return key.value unless key.nil?
end
end
def value=(value)
puts "setting value to #{value}"
Kdb.open do |db|
ks = Kdb::KeySet.new
db.get ks, "/"
key = ks.lookup @resource[:name]
if !key.nil?
key.value= value
db.set ks, "/"
end
end
end
end
end
@@ -0,0 +1,30 @@
Puppet::Type.newtype(:kdbkey) do
@doc = %q{Manipulate libelekra keys
TODO: finish this docu
}
ensurable
newproperty(:value) do
desc "The value of the key"
puts "Type: property value"
#validate do |value|
# puts "Type: property value, validate: #{value}"
# super
#end
end
newparam(:name) do
desc "The fully qualified name of the key"
puts "Type: param name"
#validate do |value|
# puts "Type: param name, validate: #{value}"
# super
#end
end
end
@@ -0,0 +1,48 @@
# Class: libelektra
# ===========================
#
# Full description of class libelektra here.
#
# Parameters
# ----------
#
# Document parameters here.
#
# * `sample parameter`
# Explanation of what this parameter affects and what it defaults to.
# e.g. "Specify one or more upstream ntp servers as an array."
#
# Variables
# ----------
#
# Here you should define a list of variables that this module would require.
#
# * `sample variable`
# Explanation of how this variable affects the function of this class and if
# it has a default. e.g. "The parameter enc_ntp_servers must be set by the
# External Node Classifier as a comma separated list of hostnames." (Note,
# global variables should be avoided in favor of class parameters as
# of Puppet 2.6.)
#
# Examples
# --------
#
# @example
# class { 'libelektra':
# servers => [ 'pool.ntp.org', 'ntp.local.company.com' ],
# }
#
# Authors
# -------
#
# Author Name <author@domain.com>
#
# Copyright
# ---------
#
# Copyright 2016 Your name here, unless otherwise noted.
#
class libelektra {
}
@@ -0,0 +1,15 @@
{
"name": "libelektra-libelektra",
"version": "0.1.0",
"author": "Bernhard Denner",
"summary": "manage your configuration through libelektra",
"license": "BSD License",
"source": "github",
"project_page": "github doc",
"issues_url": "github issues",
"dependencies": [
{"name":"puppetlabs-stdlib","version_requirement":">= 1.0.0"}
],
"data_provider": null
}
@@ -0,0 +1,6 @@
require 'spec_helper'
describe 'libelektra' do
context 'with default values for all parameters' do
it { should contain_class('libelektra') }
end
end
@@ -0,0 +1 @@
require 'puppetlabs_spec_helper/module_spec_helper'

0 comments on commit 8451873

Please sign in to comment.