Allow passing in an existing Key Vault instance

[Michael Flanakin (flanakin)]

🛠️ Description

Allow reusing a Key Vault instance in hubs

📋 Checklist

🔬 How did you test this change?

• 🤏 Lint tests
• 🤞 PS -WhatIf / az validate
• 👍 Manually deployed + verified
• 💪 Unit tests
• 🙌 Integration tests

🙋‍♀️ Do any of the following that apply?

• 🚨 This is a breaking change.
• 🤏 The change is less than 20 lines of code.

📑 Did you update docs/changelog.md?

• ✅ Updated changelog (required for dev PRs)
• ➡️ Will add log in a future PR (feature branch PRs only)
• ❎ Log not needed (small/internal change)

📖 Did you update documentation?

• ✅ Public docs in docs (required for dev)
• ✅ Internal dev docs in src (required for dev)
• ➡️ Will add docs in a future PR (feature branch PRs only)
• ❎ Docs not needed (small/internal change)

[Mubarak Tanseer (mutansee)]

Can we include additional parameter to refer a Key/secret/certificate from the Key Vault ?

[Michael Flanakin (flanakin)]

Can we include additional parameter to refer a Key/secret/certificate from the Key Vault ?

Mubarak Tanseer (@mutansee) I totally missed this comment. Can you clarify what you're asking for? Are you wanting to be able to create a new secret in the vault?

I would rather not bring in something unrelated to hubs. That can always be deployed in a parent template to extend what we have.

[Brett Wilson (MSBrett)]

Not approved. Closing this PR.