Note: we forgot to take minutes so I'm taking this from memory.

Thursday, Kirkland, 1600

Allan (@aespinosa) Rakuten, Inc.

We know that we gain a lot by leveraging community cookbooks to get our work done. But sometimes you would have to write an insane wrapper cookbooks that does all the monkey patching in order not to fork a cookbook. We know that this is just temporary until the feature were waiting for gets merged & released in a community cookbook.

But as engineers responsible to deliver actual business value to our organization we are caught in the middle.

examples:

• Get an include_recipe and monkey patch all the resources it adds to the collection to action :nothing because all you want to get in a recipe is only the service resource it exposes.
• hack around before and after an include_recipe call to consume a cookbook that needs the internet in a firewalled environment to set proxies.
• there's a cookbook you made a wrapper to to do what you want but you have another downstream one that depends on the community cookbook that now needs to depend on the wrapper. now you dont' have a choice but to fork the downstream cookbook