.
├── app
│ ├── config.pp
│ ├── install.pp
│ ├── manage_credentials.pp (defined type)
│ └── params.pp
├── app.pp (defined type)
├── config.pp
├── init.pp
├── install.pp
├── params.pp
└── service.ppI've setup the web server in a typical Package/File/Service style and perhaps its also worth noting that in the manifest/config.pp file I notify Class['web_server::service'] for each file change.
In the app.pp defined type I have the following:
define web_server::app(
$package_name,
$repo_name,
$package_version,
$credentials
) {
include web_server
class{'web_server::app::install':
package_name => $package_name,
repo_name => $repo_name,
package_version => $package_version,
} ->
class { 'web_server::app::config':
credentials => $credentials,
}
contain ::web_server::app::install
contain ::web_server::app::config
}Inside the server::app::config file i have a few Class['web_server::service'] notify statements to restart the service on app file changes. However this is causing dependency cycle errors.
Any idea where I'm going wrong with this? How do you generally manage this type of scenario? I looked at the apache forge module and it seems to be littered with Class['apache::service'] notify statements within classes/subclasses - what am I missing here?
In the app.pp defined type I have the following:
define web_server::app(
$package_name,
$repo_name,
$package_version,
$credentials
) {
include web_server
class{'web_server::app::install':
package_name => $package_name,
repo_name => $repo_name,
package_version => $package_version,
} ->
class { 'web_server::app::config':
credentials => $credentials,
}
contain ::web_server::app::install
contain ::web_server::app::config
}
Inside the server::app::config file i have a few Class['web_server::service'] notify statements to restart the service on app file changes. However this is causing dependency cycle errors.
here?