Rasbian reports back the following grain values:

local:
    ----------
    os:
        Raspbian
    os_family:
        Debian
    osarch:
        armhf
    osmajorrelease:
        8
    osrelease:
        8.0

Ubuntu reports back the following grain values:

local:
    ----------
    os:
        Ubuntu
    os_family:
        Debian
    osarch:
        amd64
    osmajorrelease:
        14
    osrelease:
        14.04

For Raspbian the osarch needed to be changed from other Debain os_family
distributions.
For Ubuntu the osrelease value is needed instead of osmajorrelease as other
Debian os_family distributions.

Part of #180

https for the ubuntu repo and option to remove /etc/salt/minion.

Signed-off-by: Rene Jochum <rene@jochums.at>

Signed-off-by: Rene Jochum <rene@jochums.at>

Signed-off-by: Rene Jochum <rene@jochums.at>

Add support for s3fs

add support for mongodb settings

Signed-off-by: Rene Jochum <rene@jochums.at>

Signed-off-by: Rene Jochum <rene@jochums.at>

Add support for OpenBSD in map.jinja

Use repo.saltstack.com in salt.pkgrepo for Debian-based distributions

add module_config for minions

JSON encode values embedded in the salt-master's configuration file

repo.saltstack.com handles all currently supported Debian releases as well
as all supported Ubuntu releases so this change should be fine.

Part of #180.

This avoids problems when values are strings containing colons. And it
mimicks what was already done for the salt-minion's configuration file.

Fixes #233.

Lxcprofile

GitPython package name is fixed for RedHat-based OS

Fixing GitPython package name for RedHat OS family. Tested on CentOS 7.

Render config as JSON

Support engine configuration

Add support for master eauth LDAP config

Ability to create non-templated cloud maps/providers/profiles

allow gitfs.keys state to function without error when no keys

add new gitfs functionality

Use the latest stable salt from repo.saltstack.com

Comment out second master config example

This second master config example was causing problems when vagrant
would use the default pillar.example

Added version check for provider/driver backwards compatibility

Renamed "provider" to "driver"

Prefix configuration files with the suitable O/S-specific pathname

Without this change, importing map.jinja in config files (as opposed to
SLS files) causes a rendering error because `slspath` isn't defined.
The `salt_settings.key_url` variable gets used only in
`salt/pkgrepo/debian/init.sls`.

add formula file this fixes #211