[chef] Re: Re: Re: deploy_revision not creating 'current' symlink?

[Jay Perry < >]

Nice, it still may be worth looking at the logs though for the last run that didn't create the symlink.  Either way glad it's working now.

On Tue, Apr 9, 2013 at 10:44 AM, Brian Hatfield < " target="_blank"> > wrote:

So for some reason making a random change and redeploying caused the 'current' symlink to appear.

On Tue, Apr 9, 2013 at 10:37 AM, Jay Perry < " target="_blank"> > wrote:

Can you also include the section of your chef log that executes this piece?  It may provide some useful info, if not try running in verbose/debug mode.

On Tue, Apr 9, 2013 at 10:32 AM, Jay Perry < " target="_blank"> > wrote:

Hey Brian,

Looking at the code that handles the creation of the 'current' symbolic link it should create a link that points to the releases/<some-release-dir>.  See the code here.  Can you paste the code from your recipe?  What version of chef are using?

Thanks,

Your Buddy :)

On Tue, Apr 9, 2013 at 9:37 AM, Brian Hatfield < " target="_blank"> > wrote:

Hi All,

Hopefully this is a silly question and I've just overlooked something in the docs, but I am attempting to use the deploy_revision resource for the first time, and I'm having a bit of trouble with the lack of 'current' being created.

Reading the docs, it says that 'shared', 'releases' and 'current' will be created, but in my case, only 'shared' and 'releases' were created, with no errors and no 'current' to be found.

Is there some option I need to enable or some flag I must pass in order for 'current' to appear?

Thank you!
Brian