Re: Conditional configuration of recipe dependent on other recipe

Alexander Kanavin

The neat way would be to include appropriate configuration into the webserver recipe, e.g. a file installed in /etc/firewall.d/ that opens the port (and nothing else).


On Tue, 16 Aug 2022 at 10:35, Maik Vermeulen <maik.vermeulen@...> wrote:

Currently we are struggling with 'interdependent' recipes.

For example: 
A webservice of ours uses a specific port, and needs to be allowed through the firewall, for which we also have a recipe.

Is there a neat way to make sure that the firewall recipe only allows that specific port if that webservice recipe is actually included in the image? And the firewall recipe should allow the port configured in the webservice recipe?

Kind regards,

Maik Vermeulen

Embedded Software Engineer — Lightyear

Automotive Campus 70 —5708 JZ Helmond, the Netherlands

This email may contain information which is privileged and/or confidential. If you received this e-mail in error, please notify us immediately by e-mail and delete the email without copying or disclosing its contents to any other person. Lightyear is a trade name of Atlas Technologies B.V. and is registered at the Dutch Chamber of Commerce under number 67264298. 

Join { to automatically receive all group messages.