I am looking to be able to give my users an static URL to a raw file in diffusion.
Basically, I've written install instructions along the lines of:
wget http://xxxx/file/data/cfgoqvp5ub2x35a6ftky/PHID-FILE-wlopi4oac3qdebppc4rt/bmsd_install.sh && chmod +x bmsd_install.sh && ./bmsd_install.sh
Ideally, this URL would always be the current version of the file bmsd_install.sh but it looks like the URL is not static because the URL that I initially used is now 404'ing.
The auth is trying to protect your code from outsiders. You can make the whole repo "public", and then there will be no auth requirement.
If you could generate an auth-free uri to download arbitrary files from your code, that would basically mean I could download all your code without any auth mechanism, just by guessing filenames.
Yeah, good point. I guess what I really want is "the ability to generate a static download URL with custom policy controls to a file in a diffusion". Looks like I should host this file somewhere else because I don't want the entire repo to be public.
Ehh, that seems messy/a lot of maintenance for a single file. It'd be perfect if you could tie a paste to a file in diffusion and handle access control through the paste since that already supports policies, but I doubt upstream has any interest in that.
I've just added a step in our deployments to push the single install file somewhere that people can download it from.