Support for git modules?

[billclark91]

First, thank you for providing this module. It has proven to be very beneficial.

We currently have several server clusters each having their own chef organization.
Example: Dev, QA, Beta, Stage, Prod.

To allow customization of environments, we separated them into individual git repositories which maintain data_bags and environments per cluster.
Example: chef-dev, chef-qa, chef-beta, etc.

All cluster repositories share the chef-cookbooks and chef-roles repositories which are include as git submodules.

Example: chef-dev repo has
data_bags/
environments/
cookbooks/ ==> submodule to chef-cookbooks
roles/ == submodule to chef-roles

I was able to 'trick' chef_diff into pulling the repository recursively by specifying url as --recursively <repoURL>

Unfortunately I don't have a 'trick' for updating submodules which requires a separate command git submodule update --recursive --remote

What's the chances chef_diff could be updated to become submodule 'aware'? If configuration uses_submodules true, then use --recursive on clone and execute the additional submodule command for updates. I would also assume the submodule revisions must be tracked separately.

Thoughts?

[desdic]

No thoughts at this moment :( but we have been talking about how we will move to the next stage where we can push a specific change to lets say 2% of servers just to see if it works but we haven't done any work on it yet

[nyerup]

@billclark91 But it sounds pretty straightforward, and as if the default behaviour could be left unchanged. Do you have a patch that implements this suggestion?