Esten Rye

@shin- got it, will do

@christopher-coffin This feature request can't be completed until the CLI supports the functionality. If you go Thumbs Up this issue, it might get some traction? https://github.com/docker/cli/issues/839

Yes, this can be changed. When I added the feature, I didn't consider that use case. I might take a look a little bit later and see what I might...

@jodygilbert I don't think you have to inject any ssh keys at all. The default `ca.json` does not configure an SSH provisioner. https://github.com/smallstep/helm-charts/blob/754c407e602965a2a0df30a56b0d58526405b46a/step-certificates/values.yaml#L44-L85 The helm chart sets the ssh certificate...

@jodygilbert you might want to checkout 1.16.1. I added the capability to optionally inject SSH keys.

This looks related to #51. I have a connect API setup for my Kubernetes clusters, I might be able to test this if I get some time to build and...

> @estenrye Thank you for the feedback, you can restrict the discovery to organizations via: > > ``` > cnspec scan github org mondoohq --discover organization > ``` > >...

@maraino I could help out with this. I already have a github action workflow you could steal for the project. https://github.com/estenrye/helm-charts/blob/main/.github/workflows/helm-publish.yaml It also auto-generates the helm-doc documentation Example: https://estenrye.github.io/helm-charts/charts/bitwarden-directory-connector/

Could someone please provide some insight as to when we can expect this chart version will release?