- #WHERE IS GROOVE AGENT 4 CONTENT FOLDER INSTALL#
- #WHERE IS GROOVE AGENT 4 CONTENT FOLDER CODE#
- #WHERE IS GROOVE AGENT 4 CONTENT FOLDER WINDOWS#
#WHERE IS GROOVE AGENT 4 CONTENT FOLDER CODE#
EnvironmentsĬode Manager (and r10k, on which Code Manager is based) uses Git repositories in a unique and sometimes confusing way. My recommendation is to use the puppet/hiera module to manage the hiera.yaml configuration, which will handle restarting the service. NOTE: Any changes to hiera.yaml require you to restart Puppet Server. One structure I recommend is discussed in this post: Hiera Hierarchies and the Custom Facts Everyone Needs. The actual Hiera directory structure is completely customizable. The default for the yaml backend with Puppet Enterprise is /etc/puppetlabs/code/environments/%/hieradata, which should be fine for most use cases. This is configured for each backend in the Hiera config file at /etc/puppetlabs/puppet/hiera.yaml. This directory is the location for Hiera data. All of these modules are named pe- to prevent namespace collisions with other modules. For stability and to ensure smooth upgrades, we ask that you keep these exactly as we installed them. /opt/puppetlabs/puppet/modules - This is where Puppet puts modules that are essential for Puppet Enterprise.There is really no good reason to use this directory, but it's worth mentioning because it’s still within the modulepath. /etc/puppetlabs/code/modules - A global modules directory that’s a holdover from before directory environments existed.This directory can also contain other internally developed modules that follow the release cadence of the control repository. This provides a separate directory in which to create two special modules labeled role and profile.
/etc/puppetlabs/code/environments/production/site - A best practice, but not the default setting.We recommend that you do not create any modules in here named role or profile. This should be utilized for component modules and Forge modules.
#WHERE IS GROOVE AGENT 4 CONTENT FOLDER INSTALL#
The first listed directory is also the default location for puppet module install, r10k and Code Manager to install modules into. /etc/puppetlabs/code/environments/production/modules - Default module directory.The example path above includes four directories: (You generally don’t want a module name to exist in two directories, and if it does, you can expect unusual behavior.) If the same module name exists in two directories, Puppet will use the code from the first module. When Puppet looks for a module, it goes through each of the above directories, in order. This can be modified in the global nf file and the environment-specific nf file. To see your current modulepath, run the following command:
Those modules can exist in multiple directories, although in general, you should use only the /etc/puppetlabs/code/environments/$environment/modules directory and the /etc/puppetlabs/code/environments/$environment/site directory if you are using roles and profiles. The vast majority of the time, the default path is fine, but it’s useful to understand what the possible paths are, and how they interact. There are a few configurable paths within Puppet. NOTE: The C:\ProgramData folder is hidden by default.Īdditionally, instead of logging going to a log file, it ends up in the application log.
#WHERE IS GROOVE AGENT 4 CONTENT FOLDER WINDOWS#
Most of the file trees are the same in Windows as they are in Linux, with the exception that they are prepended as follows: Some - but not all - of these can be redirected to a different location if absolutely required, but it’s generally discouraged. There are some minor differences between platforms, but in most cases the other directories and files used by Puppet are: (Admittedly, since the company renamed itself from Puppet Labs to simply Puppet, the naming scheme makes a bit less sense, but don't expect the directory to change to just /etc/puppet anytime soon.) (Almost) everything else Now with the all-in-one agent, we’ve unified the naming scheme. This used to be /etc/puppetlabs/puppet for Puppet Enterprise and /etc/puppet for open source Puppet prior to Puppet 4. Some of these directories can be moved others can't be moved (i.e., there's no support for moving them). Puppet installs by default into multiple directories. This article explains what each of these directories does, so you can find what you're looking for and place files where they need to be. It's not magic, but it can seem that way to new users. Beyond the language itself, there are particular directories whose purpose you need to understand to use Puppet effectively. Like any toolset, Puppet comes with its own conventions. Some of this information will also apply to older versions. NOTE: This article is targeted at versions of Puppet that include Puppet 4 - Puppet Enterprise 2015.2 and later versions.