I'm looking for enhanced support around the delivery_chef_cookbook resource, specifically to support uploading a cookbook and its dependencies (via Berksfiles and metadata.rb?) to multiple endpoints. It appears the way things are setup now, it will only upload a single cookbook, and ideally it does something similar to how the default delivery-truck publish phase works (unless there is a specific/solid reason not to!)
To be clear, I'm looking to publish/deliver cookbooks (and their dependencies) to multiple organizations/chef servers, ideally using Automate to keep these in sync, and specifically referencing the following:
Whatever the correct solution ends up being, the ideal end state (from my POV) is that after a cookbook passes and is accepted/delivered, it automatically publishes to our internal private supermarket and uploads itself(and its dependencies!) to one or more chef servers/orgs, similar to how a berks upload would work.
Hello!
I'm looking for enhanced support around the
delivery_chef_cookbookresource, specifically to support uploading a cookbook and its dependencies (via Berksfiles and metadata.rb?) to multiple endpoints. It appears the way things are setup now, it will only upload a single cookbook, and ideally it does something similar to how the default delivery-truck publish phase works (unless there is a specific/solid reason not to!)To be clear, I'm looking to publish/deliver cookbooks (and their dependencies) to multiple organizations/chef servers, ideally using Automate to keep these in sync, and specifically referencing the following:
Whatever the correct solution ends up being, the ideal end state (from my POV) is that after a cookbook passes and is accepted/delivered, it automatically publishes to our internal private supermarket and uploads itself(and its dependencies!) to one or more chef servers/orgs, similar to how a berks upload would work.
Thanks!