There are charms for proprietary software that requires restricted downloads based on license. This poses difficulties for testing, since we want the CI to be able to test these charms and want to ensure that the CI gets the same binary as the end user.
It would be good if jujuresources had support for a particular resource requiring a license key to be able to fetch, with the license key coming from, e.g., a config option. This way, we could still leverage the download, verify, and install capabilities of jujuresources, and ensure that the install process works and the user gets the same binary that was tested by the CI
There are charms for proprietary software that requires restricted downloads based on license. This poses difficulties for testing, since we want the CI to be able to test these charms and want to ensure that the CI gets the same binary as the end user.
It would be good if jujuresources had support for a particular resource requiring a license key to be able to fetch, with the license key coming from, e.g., a config option. This way, we could still leverage the download, verify, and install capabilities of jujuresources, and ensure that the install process works and the user gets the same binary that was tested by the CI