Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

munkitools5.munki.recipe munkitools_admin is an update for munkitools_core and munkitools_python? #376

Open
igor-sweet opened this issue Feb 17, 2021 · 1 comment

Comments

@igor-sweet
Copy link

I think in line 333 it should an requires and not an update_for

<key>update_for</key>

<key>update_for</key> <array> <string>%MUNKITOOLS_PYTHON_NAME%</string> <string>%MUNKITOOLS_CORE_NAME%</string> </array>

@homebysix
Copy link
Member

The Munki wiki says this about the difference between requires and update_for:

Items that declare (via update_for) they are updates for other items generally are not added to a manifest; Munki finds and applies them "automatically".

So this allows administrators to specify only one item — munkitools — in their manifest. All other munkitools-related items are found and included automatically (either because they are requirements for munkitools or declared as updates for a required package in munkitools).

The part I'm not super clear on is how administrators can opt out of deploying the admin tools to a specific manifest. The munkitools_admin pkginfo isn't overrideable, so I suppose one method would be for the administrator to create a duplicate of the munkitools5.munki.recipe locally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants