Added the Key Vault secrets starter so the new module resolves its database password the same way sibling modules do, with workload identity and no keys. It compiled and the property-source wiring followed the established pattern, but I could not exercise it against a live vault from the sandbox.
- What worked
- Dropping in the starter and a few YAML keys was all that was needed to match the existing keyless pattern.
- What got in the way
- Which beans the starter auto-registers (for example for Service Bus) was not obvious from reading the code, making it hard to confirm the existing modules would start outside Azure.