Add v1.0.2 of ncsa/puppet-profile_firewall
Update puppetlabs/firewall from 2.5.0 to 3.0.0
Add data/role/puppet-master.yaml to set profile_firewall::ignores heira data
so that docker firewall rules are not removed from puppet masters
Include profile_firewall in base.pp
Use fqdn for telegraf agent hostname
Add telegraf_sslcert_check & telegraf_website_check to profile puppet-master
Add lookup options for profile_monitoring::telegraf::inputs_extra parameters
Update profile_monitoring to tag v0.1.5
Add basic sssd data for NCSA
setup common NCSA settings for SSSD
Setup sssd debug_level
Add profile hiera data
enable and include profile_allow_ssh_from_bastion
enable ncsa/sshd
added groups for allow_ssh_from_bastion to control repo
Remove simple_allow_groups from default sssd and let ssh add them
Add default bastion_nodelist to control repo
Upgrade concat module
include ::pam_access
point to latest tag of profile_pam_access
point profile_pam_access to topic branch
Update to ncsa/sshd v0.3.0
Update profile_allow_ssh_from_bastion to v0.2.0
Update profile_pam_access to v0.0.4
Catalog compilation succeeds and deploys for role::default
add profiles additional_yum_repos and additional_pkgs
puppetlabs/stdlib
move some includes from profile::base to role::default
Prior to this commit, we placed modules local to a users installation
in the `site` directory. This was just a convention and the name
`site` doesn't clearly convey what it is for.
After this commit, we place modules local to a users installation in
the `site-modules` directory. This makes it more clear to users
that this is a directory that modules go i. When users start
with bolt they won't even know what a control-repo is and
renaming site to site-modules gives them a better idea of why
they should put their modules with tasks in them. Also see:
https://tickets.puppetlabs.com/browse/BOLT-1108
