Sharing state across an environment


#1

I’ve got internal and external webserver roles. In my internal run list I
have a recipe for a web service which sets a node attribute with that
services end point. I’ve got other web app recipes later in the internal
run list that use that web service end point attribute in configuring the
web apps. I also have a recipe in the external web server role that wants
to discover the end point for that web service, but I’m not sure how to
access the other nodes attributes or even if I should.

Is there a way that I can set the web service end point attribute at an
environment level and have my recipes access it from there? Is there a
better way to handle this need?

Thanks,
Dwayne


#2

Welp just found the answer to my first question. Having my recipe search
for nodes within my environment that have my web service recipe in their
run list looks like it would work.

On Mon, Jan 26, 2015 at 2:03 PM, Dwayne Forehand dwayne@4handsclapping.com
wrote:

I’ve got internal and external webserver roles. In my internal run list I
have a recipe for a web service which sets a node attribute with that
services end point. I’ve got other web app recipes later in the internal
run list that use that web service end point attribute in configuring the
web apps. I also have a recipe in the external web server role that wants
to discover the end point for that web service, but I’m not sure how to
access the other nodes attributes or even if I should.

Is there a way that I can set the web service end point attribute at an
environment level and have my recipes access it from there? Is there a
better way to handle this need?

Thanks,
Dwayne