munkiserver
munkiserver copied to clipboard
Add file-based munki server import functionality
I propose this be moved to a later time. Perhaps v.8 or .9
Has any progress been made on this? How would this be implemented? I'm gradually learning Ruby, and this is a very key feature for me so I'd be happy to give it a try developing it. Would just importing a compiled catalog from munki work?
I haven't worked on this. Jordan was going to take a stab at it. It's a pretty interesting problem to try to solve. I think the easiest would be providing a ruby rake task to do this. No need to design a nice web based interface, you'll only do this once, right?
You'll need to point it at a repository, parse the catalog (which will be a mighty challenge), create Packages, Package Branches, etc based on the catalog -- ensuring to move the related .dmg file into the munkiserver assets folder. Quite a tall order, but something that is crucial to new Munki admins coming to MunkiServer.
If you build a branch in your repo, I can take a look as things proceed.
Ricky
On Dec 4, 2011, at 5:16 PM, treydock wrote:
Has any progress been made on this? How would this be implemented? I'm gradually learning Ruby, and this is a very key feature for me so I'd be happy to give it a try developing it. Would just importing a compiled catalog from munki work?
Reply to this email directly or view it on GitHub: https://github.com/jraine/munkiserver/issues/92#issuecomment-3009355
I haven't dug into this task yet. There have been several requests for this, which is why I moved it to 0.7. Originally, I was planning to leave it until just before 1.0, but after a few folks asked about this, I realized that it may be advantageous to have a more administrators onboard before 1.0 to help provide bug reports, suggestions for improvement, and even commits.
Jordan, are you making this a rake task or something in the web interface?
This would be called using a rake task. It would happen so rarely and only by a sysadmin that methinks a cmd line makes most sense.