Hi,
this would even work, but I think the approach as a whole is not well in
line with puppet's philosophy. Application deployment is not among its
core strengths.
If you really want to do this by puppet, I suggest you keep it simple:
1. perform all your steps in one monolithic script
2. have puppet deploy the script and execute it
3. give puppet the ability to determine if the script needs running,
typically by first comparing the deployed version to the desired one, e.g.
$version = "0.2-5"
exec { "deploy-app --version=${version}":
unless => deploy-app --check --version=${version}"
...
}
HTH,
Felix
On 11/20/2013 05:08 PM, Sergey Arlashin wrote:
> You can create some sort of a trigger file. Like this:
> file { "/some/folder/file_trigger"
> ensure => present,
> content => "version01",
> …
> }
>
> Add "refreshonly => true" to your resources. Then subscribe your
> resources to this file. Once the file is changed, your code will be
> executed.
> 1. stop application service
> 2. take backup of existing application
> 3. download application artifact
> 4. install the application
> 5. some configuration stuff
> 6. start the application service
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/528DE6C9.3020507%40alumni.tu-berlin.de.
For more options, visit https://groups.google.com/groups/opt_out.
