We have upload new recipes via cookbook upload. When we go through the
webui to edit a role and then drag those newly created recipes, the recipes
do not show up in the list of available recipes. Over the course of about
an hour they do eventually appear.
I assume the webui or erchef is caching data. Is there a configuration
option that would allow us to set a more aggressive TTL? We saw
erchef[‘cache_ttl’] but it is not descriptive as to what this will actually
do and if this value is responsible for our issue.
-.mag
Mark Garcia Cloud Operations Managermark.garcia@gravitant.com o:
512-831-3939
m: 206-349-5778Just In Time I.T. http://www.gravitant.com
So, looks like we figured it out. Turns out the recipe list will only show
the recipes available for the highest versioned cookbook. We sandbox our
recipes with version 999.+ and we commit to versions <999. This recipe was
committed to <999 and didn’t show up.
-.mag
–
Mark Garcia Cloud Operations Managermark.garcia@gravitant.com o:
512-831-3939
m: 206-349-5778Just In Time I.T. http://www.gravitant.com
On Thu, Nov 7, 2013 at 10:55 AM, Mark Garcia mark.garcia@gravitant.comwrote:
We have upload new recipes via cookbook upload. When we go through the
webui to edit a role and then drag those newly created recipes, the recipes
do not show up in the list of available recipes. Over the course of about
an hour they do eventually appear.
I assume the webui or erchef is caching data. Is there a configuration
option that would allow us to set a more aggressive TTL? We saw
erchef[‘cache_ttl’] but it is not descriptive as to what this will actually
do and if this value is responsible for our issue.
-.mag
Mark Garcia Cloud Operations Managermark.garcia@gravitant.com o:
512-831-3939
m: 206-349-5778Just In Time I.T. http://www.gravitant.com