[Datastore] Extend Azure blob to support other auth methods

[hayesgb]

Currently, the only supported authentication methods against AzureBlobStore is AZURE_STORAGE_CONNECTION_STRING. , and possibly AZURE_STORAGE_KEY. This enables other authentication methods including use of ServicePrincipals and SAS tokens.

[hayesgb]

Proposed fix for #1141

[Hedingber]

Hi @hayesgb
Thanks a lot for the contribution!
I asked @theSaarco to review it, in the meanwhile, I see that the lint CI failed,
Did you follow the instructions on https://github.com/mlrun/mlrun/blob/development/CONTRIBUTING.md and specifically running make fmt and make lint ?
Let me know if you're having any trouble with this

[theSaarco]

@hayesgb, thank you for contributing.
In terms of testing, we have a manual integration test located in tests/integration/azure_blob/test_azure_blob.py - these tests are manual since they require you to provide access parameters for the Azure storage account you wish to test against. These details are given in a yml file in the same directory.
Given that you've added new access modes which use different parameters, please add the option to specify these parameters in this test, so it can be used to test your new additions. Please let me know if you need assistance for this.

[hayesgb]

As a side-note, when I try to run make test-dockerized on my local machine, I'm getting the following error:

#5 1.083 E: The repository 'http://security.debian.org/debian-security buster/updates InRelease' is not signed. #5 1.083 W: GPG error: http://deb.debian.org/debian buster-updates InRelease: At least one invalid signature was encountered. #5 1.083 E: The repository 'http://deb.debian.org/debian buster-updates InRelease' is not signed.

Do you recommend I assume this is trusted?

[Hedingber]

@hayesgb I've never encountered this error, googling it brought up this one https://stackoverflow.com/questions/62473932/atleast-one-invalid-signature-was-encountered
I would start with the suggestions there (Cleaning caches and images) before manually "making it trusted"
BTW, note that the reason CI doesn't run automatically on all of your commits (it's running only when I approve) is because you're a first time contributor, once we'll merge one of the PRs, it will be more comfortable.
Another thing on that regard, CI passed successfully 🥳

[hayesgb]

Thanks @Hedingber -- Do I need to make any additional changes at this point? Can we consider the requested azure_connection_configured() update completed?

[theSaarco]

@hayesgb - I'm fine with the changes done so far. I have some ideas for improving the test further, but no reason to block this PR for them at this point. 🎉

[Hedingber]

@hayesgb
PR was merged, you're officially an MLRun contributor now 🎉