On Tuesday, March 12, 2013 at 10:54 PM, wrote:
Sorry if this is a totally dumb question, but I can't seem to find the answerout there. I was hoping to try and leverage the deploy resource for a simpleapp I've got in git. I've been through the docs athttp://docs.opscode.com/resource_deploy.html and I have things working for themost part.The question I have is about expected behavior. It appears that every singlechef run the resource is taking action (including restarting the app) despitethe fact that no changes are pushed to the github repo. We run Chef client on aschedule, so I'd hate to have the app "deployed" every time chef runs.So my question is if this is expected or am I doing something wrong? On thesurface this sure doesn't feel very idempotent, and given the general push toensure resources are idempotent this caught me a little of guard.Here is the uber basic recipe:deploy "/my/path" dorepo "git://my_git/my_org/my_app.git"migrate falsesymlink_before_migrate({})restart_command "service httpd restart"endLog Entries:INFO: Processing deploy[/my/path] action deploy (cookbook::default line 15)INFO: deploy[/my/path] copied the cached checkout to/my/path/releases/20130313024211INFO: deploy[/my/path] made pre-migration symlinksINFO: deploy[/my/path] purged directories in checkout log, tmp/pids,public/systemINFO: deploy[/my/path] created directories before symlinking tmp,public,configINFO: deploy[/my/path] linked shared paths into current release: system =>public/system, pids => tmp/pids, log => logINFO: deploy[/my/path] made pre-migration symlinksINFO: deploy[/my/path] linked release /my/path/releases/20130313024211 intoproduction at /my/path/currentINFO: deploy[/my/path] updated symlinksINFO: deploy[/my/path] restarting appINFO: deploy[/my/path] removing old release /my/path/releases/20130313022329INFO: deploy[/my/path] deployed to /my/path
Archive powered by MHonArc 2.6.16.