baloise.github.io

gitblit.org

Gitblit

http://www.gitblit.org/eclipse_plugin.html

Gitblit as a viewer. Using the Eclipse plugin. Replication and advanced administration. Bintray (1.4.0 ). GoogleCode (pre-1.4.0). Gitblit SSH and Plugin Management asciicast. GitMinutes #29: James Moger on Gitblit. There is an Eclipse plugin,. Provided by the Baloise Group. Support for multiple Gitblit servers. Copying git repo urls to the clipboard. Or via drag&drop to any drag&drop enabled target as text (or as type URL). Integration with the EGit Clone Wizard. Source Code and Issue Tracker.

gitblit.com

Gitblit

http://www.gitblit.com/eclipse_plugin.html

Gitblit as a viewer. Using the Eclipse plugin. Replication and advanced administration. Bintray (1.4.0 ). GoogleCode (pre-1.4.0). Gitblit SSH and Plugin Management asciicast. GitMinutes #29: James Moger on Gitblit. There is an Eclipse plugin,. Provided by the Baloise Group. Support for multiple Gitblit servers. Copying git repo urls to the clipboard. Or via drag&drop to any drag&drop enabled target as text (or as type URL). Integration with the EGit Clone Wizard. Source Code and Issue Tracker.

jerakia.io

Quick start Tutorial

http://jerakia.io/tutorial/config

Writing custom lookup plugins. 30 second spin up! Jerakia reads it’s initial configuration from. By default. At the very minimal we need to confgure the loglevel information and the locations of the logfile, policy directory and plugin directory. Mkdir /etc/jerakia $ vim /etc/jerakia/jerakia.yaml. Next: Create a Policy. Hosted by GitHub Pages.

jerakia.io

Quick start Tutorial

http://jerakia.io/tutorial/override

Writing custom lookup plugins. 30 second spin up! Populate the data in the hierarchy. Now let’s provide some different data further up in our hierarchy, for example, we shall override. In our dev environment. Mkdir -p /var/lib/jerakia/environment/dev $ vim /var/lib/jerakia/environment/dev/apache.yaml. Query from the command line. If we run the same query command as before, we expect to get the same output. Jerakia lookup port - namespace apache. Next: Integration with Puppet. Hosted by GitHub Pages.

jerakia.io

Datasources

http://jerakia.io/datasources/file

Writing custom lookup plugins. 30 second spin up! The file data source performs hierarchical searches across YAML or JSON formatted files and searches for the lookup key. The file format, one of :yaml and :json (other formats are pluggable). The root of the documents. An array specifying the order of hierarchical lookups. Entries starting with an alphanumerical character will be relative from. Overrides the default extension (eg: yml) for the file format chosen. Key = "port", :namespace = [ "apache" ], }.

jerakia.io

Quick start Tutorial

http://jerakia.io/tutorial/puppet

Writing custom lookup plugins. 30 second spin up! As a Hiera backend. Jerakia can be configured as a Hiera backend. Or add it as an additional data source:. As a Puppet data binding terminus. If you are migrating an existing, or unknown code base we would recommend you keep Hiera configured as a backend to catch any lookups that are made with the. Functions. But for all other lookups you can route them straight to Puppet by bypassing Hiera altogether and using Jerakia as a data binding terminus.

jerakia.io

Quick start Tutorial

http://jerakia.io/tutorial/data

Writing custom lookup plugins. 30 second spin up! Datasource as configured earlier we can add our data to YAML files under the directory specified in. Which we set to. It’s recommended that you read Jerakia Lookup Basics. To understand the structure and behaviour of a Jerakia lookup. Understanding the file datasource. Format = :yaml, :docroot = "/var/lib/jerakia", :searchpath = [ "hostname/#{scope[:fqdn]}", "environment/#{scope[:environment]}", "common" ]. If our scope contains the following. Let’s start...

jerakia.io

Quick start Tutorial

http://jerakia.io/tutorial/policy

Writing custom lookup plugins. 30 second spin up! Jerakia policies are containers for lookups. When a lookup is invoked against Jerakia it can select a policy to use, by default, if no policy name is given then Jerakia will look for a policy called. Policy files live within the directory defined in. So let’s create an empty policy. Mkdir /etc/jerakia/policy.d $ vim /etc/jerakia/policy.d/default.rb. Next: Write a lookup. Hosted by GitHub Pages.

jerakia.io

The `jerakia` command

http://jerakia.io/basics/cli

Writing custom lookup plugins. 30 second spin up! Display jerakia version information. The lookup subcommands take a third argument as the key followed by options. Jerakia lookup key [options]. C, [- config=CONFIG]. Specify a different configuration file from the default (. P, [- policy=POLICY]. Specify a policy to use for the lookup, default: default. N, [- namespace=NAMESPACE]. Namespace of the request key being looked up. T, [- type=TYPE]. The type of lookup, the default type of. S, [- scope=SCOPE].

jerakia.io

Quick start Tutorial

http://jerakia.io/tutorial/lookup

Writing custom lookup plugins. 30 second spin up! Jerakia policies contain lookups that run in order. A lookup must contain, at the very least, a name and a datasource to use for the lookup. The current datasources that ship with Jerakia are. The file datasource takes several options, including format and searchpath to define how lookups should be processed. Within the lookup we have access to. We will start by using the. Vim /etc/jerakia/policy.d/default.rb. Here we have described the.