Issues an ephemeral X.509 certificate from the Vault PKI secrets engine and writes the PEM-encoded components to temporary files in the build workspace.
-----BEGIN CERTIFICATE-----), followed by the intermediate CA certificates
(without the root). This is the client certificate chain that tools such as curl, Docker
or Go present during mutual TLS; for a root-only PKI it contains just the certificate.0400 permissions on POSIX systems and restricted to
the file owner on Windows; the build fails if the permissions cannot be applied.
Do not print the file contents to the build log.ca_chain), or the
issuing CA certificate for a root-only setup.
All three files come from the same Vault issuance and are automatically deleted when the
withCredentials block exits.
Tip: For tools that accept a PKCS12 keystore, use the standard Certificate binding (keystoreVariable / passwordVariable) instead – it also works with Vault PKI credentials.