Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to locate keys/ (acme_certificate_keys_path)? #22

Open
jwhimpel opened this issue Feb 25, 2022 · 1 comment
Open

How to locate keys/ (acme_certificate_keys_path)? #22

jwhimpel opened this issue Feb 25, 2022 · 1 comment

Comments

@jwhimpel
Copy link

I have written a playbook that in turn uses this collection. I am beginning to discover that it is necessary to add certain parameters in the playbook (i.e. become: true). Currently, the playbook is failing when the community.crypto.openssl_privatekey (line 50 in main.yml) fails since the "path" parameter is a relative pointer. My knowledge of ansible is not sufficient to allow me prefix this relative parameter with the base directory name to prepend to the relative path given in the path parameter.

The error message reads: FAILED! => {"changed": false, "msg": "Error while reading file "keys/acme-account.key": [Errno 2] No such file or directory: 'keys/acme-account.key'", "other": {}}

The absolute directory would be /etc/ssl/keys. How do I prepend the "/etc/ssl/".

Thanks.

PS: As an intermediate level ansible user, I find your collection well architected and well-documented. As a learning example, it provides with with a very high bar to which my work should strive to achieve. :-) Thanks.

@felixfontein
Copy link
Owner

@jwhimpel thanks for your feedback!

Have you tried setting acme_certificate_keys_path to an absolute path like /etc/ssl, and acme_certificate_acme_account to an absolute filename like /etc/ssl/acme-account.key?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants