Since I recently built and added an Adobe Acrobat Pro DC installer to my Munki repo and enabled your Acrobat Pro DC Updater recipe with the intent that it automate updates for this, this is the actual first time Adobe have issued an update and therefore the first time your recipe has been needed.
I encountered two issues, arguably these are not bugs but I am reporting them so you can consider them and if needed make modifications.
The first issue was that your recipe defines the path as pkgs/apps/adobe/......
It should be noted that an existing Acrobat Reader recipe and my Acrobat Pro installer recipe both assume a path of pkgs/apps/Adobe/.... which as you can see has Adobe with an uppercase A. As I am using a Linux based server to host my Munki repo which is case sensitive, this does have an impact. I have worked around this by in my override recipe changing the path to pkgs/apps/Adobe/....
The second issue is that your Munki recipe defines the 'Requirements' as being an update for 'Adobe Acrobat Pro' that is a Munki installer 'named' Adobe Acrobat DC. In my case my recipe uses the name AdobeAcrobatDC, again I have worked around this via my override recipe.
Whilst the second issue is I suspect more down to how I created my Acrobat Pro DC installer recipe, the first issue might be more of an issue worthy of investigation and resolution.
Since I recently built and added an Adobe Acrobat Pro DC installer to my Munki repo and enabled your Acrobat Pro DC Updater recipe with the intent that it automate updates for this, this is the actual first time Adobe have issued an update and therefore the first time your recipe has been needed.
I encountered two issues, arguably these are not bugs but I am reporting them so you can consider them and if needed make modifications.
The first issue was that your recipe defines the path as pkgs/apps/adobe/......
It should be noted that an existing Acrobat Reader recipe and my Acrobat Pro installer recipe both assume a path of pkgs/apps/Adobe/.... which as you can see has Adobe with an uppercase A. As I am using a Linux based server to host my Munki repo which is case sensitive, this does have an impact. I have worked around this by in my override recipe changing the path to pkgs/apps/Adobe/....
The second issue is that your Munki recipe defines the 'Requirements' as being an update for 'Adobe Acrobat Pro' that is a Munki installer 'named' Adobe Acrobat DC. In my case my recipe uses the name AdobeAcrobatDC, again I have worked around this via my override recipe.
Whilst the second issue is I suspect more down to how I created my Acrobat Pro DC installer recipe, the first issue might be more of an issue worthy of investigation and resolution.