“Or are you asking for BigFix to provide a GIT client and associated logic for it through the relay chain?”
Yes I believe we would want it to be processed through the relay chain, with the bigfix master pulling from GIT to relay to client.
I believe it could be something as simple as adding the options of user id and password for the master to use to pull from the GIT/NEXUS repo. This could be setup similar to have other download plugins are configured with an ini file with the user and encrypted password to use. like AIXProtocolR2
Then the prefetch would just be like url=AIXProtocolR2:/website/filename.txt
And it would use the user and encrypted password associate with that plugin.
I believe we use something like this to pull openssl down from IBM through the bigfix master to relay to client…
prefetch openssl-126.96.36.1990.tar.Z sha1:a4433f26a06e4e272248170b6a61ba23d312ffe6 size:34883100 AIXProtocolR2://get.file/openssl/openssl-188.8.131.520 sha256:05061bbe92afc0833b91986280f6c389a04f626db8a61d4497528833df79b511
Unless there is a way to do the prefetch and pass it a ini file that has that user and password in it?