Clay Rosenthal

@ethan-deng Will this be merged if you've approved it? seems like a helpful addition

+1, also does not respect the context flag when configuring a user ``` ❯ step context select dev ✔ Context: dev ❯ step ssh config --roots --host --context dev ecdsa-sha2-nistp256...

Oh nice. I'll look into that and maybe make it more generic file/directory syncing with a dotfile sub command. Thanks for the pointer

I have a setup that I can use to test this with, but unsure how to build this binary given its separate from the main certificates repo

@JayGhiya I see you've merged #1186 and #1177 , is there a PR for the documentation on how to use these helm charts? Or are they still a work in...

So currently if we want to use them, we'd just clone locally them helm install from the local file path? There's no helm repo to add? ie: ``` git clone...

Any update on this? The solution below seems pretty reasonable to me > Solution I'm thinking of is (cross-posting from [#133 (comment)](https://github.com/aws/amazon-eks-pod-identity-webhook/pull/133#issuecomment-1017907120) for awareness, apologies again for all the noise):...

Hey @dopey, the purpose would be having multiple servers serving from one database, with only one having permissions to create and destroy tables. A side effect would be more descriptive...