Closed ablotim closed 2 years ago
+1
+1
👍
@shinmog or anyone else could successfully use the new resource "panos_certificate_import"
? I get a "Failed to extract certificate" whereas I can import certificates in the Panorama GUI using same files and passphrase. Thanks !!
@amemni
Open a new issue please. Commenting on closed issues reduces visibility.
@amemni
To answer your question tho, yes, I've tested this with both PEM and PKCS12 style certificates and it's worked for me. If it's not working for you, please be sure to include your plan file for the import in your new issue removing the passphrase.
It has been years but if anyone needs an example of how to use acme_cerficate with kubernetes_secret trough terraform... this is the example ^^^
thanks @ablotim
Is your feature request related to a problem?
We already use terraform to create our acme/letsencrypt certificates and distribute them to k8s. It would be nice to be able to push to our Palo Alto system in the same way, eg. for globalprotect. In the Palo Alto config it should create an entry under "shared certificate".
Describe the solution you'd like
Ideally it should be equally simpel as other systems that use the same certificates, eg.
after which you can you "mycert" in other configs like globalprotect, and it will be updated automatically together with the other certificates.
Describe alternatives you've considered
acme.sh can already push to panos, which works great. However, in everyday use we found a terraform solution to be more reliable, not so much because of any issues with acme.sh, but because any issues are much more visible when terraform throws a fit whenever anyone tries to update any infrastructure.
Additional context
For internal usage it's fine to use an internal-only ca. For things like globalprotect however, a 'real' certificate is much better. It would be nice if we could manage it automatically.