Add support for azure keyvault backend

[Wiston999]

Status

READY/

Migrations

NO

Description

Add support Azure KeyVault secrets backend.

List of fixes # (issue)

Type of change

Please delete options that are not relevant.

• [ ] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Provide instructions so we can reproduce.

Please also list any relevant details for your test configuration

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [ ] Any dependent changes have been merged and published in downstream modules

[codecov-commenter]

Codecov Report

Merging #87 (5490e83) into master (c293ef2) will decrease coverage by 4.07%. The diff coverage is 57.69%.

@@            Coverage Diff             @@
##           master      #87      +/-   ##
==========================================
- Coverage   85.26%   81.19%   -4.08%     
==========================================
  Files           9       11       +2     
  Lines         482      553      +71     
==========================================
+ Hits          411      449      +38     
- Misses         53       86      +33     
  Partials       18       18              

Impacted Files	Coverage Δ
errors/errors.go	100.00% <ø> (ø)
backend/backend.go	76.00% <33.33%> (-24.00%)	:arrow_down:
backend/azure_kv.go	47.05% <47.05%> (ø)
backend/azure_kv_metrics.go	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update c293ef2...5490e83. Read the comment docs.