As it stands, provisioning each connection creates its own tailscale auth key. We store that key in AWS SSM for AWS connections, and we wanted to store that key in KeyVault for Azure, but it takes too long
We could alleviate this by creating an connecti azure init command which provisions the required keys for us. We could then expose these via stack references.
This gets a little tricky, because now we need multiple projects. We'll consider this for v1.0.0
As it stands, provisioning each connection creates its own tailscale auth key. We store that key in AWS SSM for AWS connections, and we wanted to store that key in KeyVault for Azure, but it takes too long
We could alleviate this by creating an
connecti azure init
command which provisions the required keys for us. We could then expose these via stack references.This gets a little tricky, because now we need multiple projects. We'll consider this for v1.0.0