Maciej Delmanowski

I'm not sure if this is a good check, but I'll look into it.

`debops.ferm` uses data gathered by `debops.core` role to allow connections from Ansible Controller. `debops.core` is a required role, so if you only want to use specific playbooks with a host...

You can do the PR yourself. :-) If you do, please do it against the [DebOps monorepo](https://github.com/debops/debops/) so it can be included in the future documentation, when it's updated and...

At the moment the PKI scripts are designed to not expect any changes in the realm configuration. You cannot modify an existing X.509 certificate without creating a new one, so...

It seems to be an [issue with Ansible and non-POSIX filesystems](https://github.com/ansible/ansible/issues/9526) mounted by Vagrant. Seems to be quite a popular bug when Ansible is messing with the shared folders... For...

@thiagotalma Not using Vagrant shared folders for DebOps `secret/` directory should solve this issue. For example try using an NFS-mounted share stored in a Linux host.

Sounds like one of the `kubernetes_*` variables is a dictionary instead of a string. Check all of them to see their value during the role execution by setting some `debug`...

Can you show the debug value of `custom_pki_realms` variable?

Well, hmm, they look ok... How about this - can you remove all subject_alt_names that contain any variables and see if the result works? Just to eliminate any other issues...

And the normal `debops.pki` role runs fine? If yes then I'm out of ideas... How about this, before that problematic task, add: ``` yaml - name: Show all the things...