We deploy this image on our K8s cluster using Helm charts, where the PEM encoded key is a generated on deployment and is a K8s secret. Helm can't work with keys generated on install and paste the content in the Nginx configuration (because it's being generated in the same operation). One solution would be to map the secret onto a file and use that path as a mounted volume.
Would reading the PEM file from a file be a new feature in this plugin?
I've already forked the repo and added two attributes that load the key, it serves us well. If it's cool for you I can make a PR to include it officially?
Hi!
First off, nice plugin, saves a lot of trouble! 👏
We deploy this image on our K8s cluster using Helm charts, where the PEM encoded key is a generated on deployment and is a K8s secret. Helm can't work with keys generated on install and paste the content in the Nginx configuration (because it's being generated in the same operation). One solution would be to map the secret onto a file and use that path as a mounted volume.
Would reading the PEM file from a file be a new feature in this plugin?
I've already forked the repo and added two attributes that load the key, it serves us well. If it's cool for you I can make a PR to include it officially?