Joe Wilner

Hi @johanbrandhorst. Yes, we need an empty common name because we rely on URI SANs. I configure `Certify` as follows: ```go c := certify.Certify{ Issuer: &issuer, RenewBefore: time.Hour * 24,...

Effectively, yes, the client certificates must not have a common name set. For context, I'm prototyping an mTLS authentication arch and effectively in control of both the PKI (vault) and...

Hi @abompard -- thanks for the PR. We'd like to land it but are going to need spend some time reviewing and testing it. Along those lines, I'd like to...

Oh and the issue is pretty clearly here: https://github.com/knative/client/blob/release-0.19/pkg/kn/commands/service/apply.go#L69

@rhuss I don't immediately remember what my need for revision-name was. I can dig into it some more and get back to you. In the meanwhile, you can see our...

I'll just chime in that docker is of course a massive dependency, but it's also an extremely common dependency in the modern software toolbox. Our generation logic for SQLBoiler already...

@firstof9, thanks, I’ll check out those keymaster events you suggest. Do you think using those events would simplify the configuration so that I wouldn’t have to keep three different locations...

@firstof9 based on the [code](https://github.com/FutureTense/keymaster/blob/a35388b0d269ba8f4487247f8d799989c442bcc0/custom_components/keymaster/helpers.py#L336-L351), it looks you enrich the event w/ the name values from the configuration. That suggests that I could use a naming convention for slots across...

Thanks @firstof9 I'll bring up in the thread if there are any opportunities for improvement, but I've got a baseline working here. I name code slots with `BOTH-DOORs` in the...

@firstof9 ya thanks, good tip. For posterity: https://community.home-assistant.io/t/keymaster-z-wave-lock-manager-and-scheduler/166419/2875?u=jwilner