search

autopkg / filewave

FileWave recipes for AutoPkg, allowing admins to automatically import/update packages into FileWave
17 stars 15 forks source link

I have more of a workflow issue #22

Open joncohen opened 7 years ago

joncohen commented 7 years ago

I've been using a mix of import recipes from here as well as ones that I have written. I'm coming from the Munki world where there is a common name key that tells Munki what is going on. With the FW imports, I'm getting filesets that are numbered based on each version, as well as new fileset IDs.

Since they are new filesets, I lose my associations and the clients don't get the update.

How do you work with this since I assume that you all use the recipes that you post here?

I know that I can import them to a group, and associate the fileset group to my clients but if I go that route, I lose the kiosk functionality or I will conversely need to manually update the kiosk.

Any feedback would be appreciated.

nielshojen commented 6 years ago

I'm kinda in the same boat. I do my kiosk fileset with an empty fileset with the actual fileset as a dependancy. That way i can just switch the dependancy to newer version. To fully automate the update process, it would be nice to be able to modify dependancies in a recipe.

joncohen commented 6 years ago

This was actually user error on my part, we dump all filesets for a given application or set of applications into a fileset group now. We then associate the group with the client or client group and then turn kiosk on for the group as a whole. All contents of that fileset group are available via kiosk.

joncohen commented 6 years ago

We then use the fw_fileset_group key in our recipes to allow AutoPkg to send files directly into the correct FileSet group when a new version comes out.