jocads.sh - Command Line Options - --dest-list All Instances

[wreck-gar]

Howdy,

How do I specify all destination instances when using the command line options?

I've tried using --all-instances but I'm not sure of the correct usage and it always prompts me to choose a destination instance.

I can get it to work if I specify a single destination instance, like this -

./jocads.sh --source-list 'dev' --source 'https://123.jamfcloud.com' --dest-list 'prd' --dest 'https://456.jamfcloud.com' -c --package=Firefox-123.0.pkg --confirm --clean

Thanks.

[grahampugh]

The command line options of jocads are not fully featured in comparison to the interactive options. I only ever implemented the --all option for policies, as that was the use case I had at the time. Nowadays I exclusively use jocads interactively.

Bear in mind also that jocads only copies package metadata. It doesn't copy packages themselves. Again, that's because my use case when developing the tool was on-prem Jamf Pro instances with a common file share distribution point. I do want to look at extending the functionality to copy packages using the new Jamf Pro API packages endpoint at some point. Watch this space.

[wreck-gar]

Ahh all good, at least I know I am not going crazy, maybe.

I have a similar use case and am only interested in the package meta data. Basically, if I update an App with the same filename, then I need to update the meta data for all instances so the package validation does not fail (or I could disable package validation for all clients).

As a work around I have a wrapper script that cycles through the instances and updates the packages, but I thought the CLI option would be cleaner. Alternatively, I guess I could create a common policy just for updating the meta data and copy that policy to all instances as a work around.

An all instances option would also be good for deleting old versions of packages from all instances.

Thanks for your work.