ttl Posted February 23 Share Posted February 23 Does the API support such a scenario? We're seeing some instances where something like a printer driver gets lost (as of right now, assuming it's something the user is doing because it's not widespread, but happens enough that it's gotten to be something we'd like to script a fix for) and because those are sent as a pkg, they don't get re-downloaded on verify. After the pkg is installed, the original installer disappears. In /usr/local/etc/FileWaveInstallers/FlatPackage-958_658e_558_368_367_109.pkg on first deployment, there's a 21MB file: 958_658e_558_368_367_109.pkg After installation, 958_658e_558_368_367_109.pkg is gone and only FileWave.plist remains If, on verify, a condition is met in a bash script, I'd like to re-download 958_658e_558_368_367_109.pkg and install it Alternatively, is there a flag to set on the pkg to leave it behind after installation so I can simply point the script to it & re-run? The API documentation seems to only reference querying and obtaining report-like data: https://fwkb.atlassian.net/wiki/spaces/KB/pages/4328035/RESTful+API Link to comment Share on other sites More sharing options...
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now