We want to deploy a file to the client.
But the file would update on the server.
We found that if the file is updated, the task still re-deploy the old file not the newest file.
How could we let bigfix to always deploy the new file to client?
There are several ways to do dynamic downloads. Each has pros and cons and can be useful depending on the situation. I’ve used all of them.
‘download now as’ - If you use this option, it will instruct the Bigfix client to use a native actionscript command to do the download, however it will go directly to the requested url, bypassing the relay infrastructure. You can do relevance substitution in the url if desired. See this post for an example.
WGET - This is a versatile utility that allows many download options.
CURL - Also another good utility with several different options.
Choose whichever way best suits your situation. I find when using WGET or CURL it is helpful to embed it into dynamically generated script where I can do relevance substitution.
As mentioned, there are trade-offs with each method. The three choices I described allow full range of choices both in terms of how you get the content and the parameters around your download choices. To Aram’s point, they don’t check files hashes, etc. There are situations where security is sensitive and the content is semi-dynamic where Bigfix’s native ‘Dynamic Download’ is a good choice, such as a periodic definition file.
The options I described work well for more trusted, lower security risk data, and highly dynamic content. For example, we use Bigfix in a business process automation workflow where we get dynamic data from backend ERP type systems. As the data is continuously unique, it doesn’t work to create a manifest as it would be perpetually out of date.