SearchVarnish Controller
Handle certificates
Handle TLS certificates, such as listing, add, delete or update.
Examples:
vcli certificate list
vcli certificate ls -f id=1
vcli certificate ls -f name="MyCertificate*"
vcli certificate add mycert --cert /path/to/certificate.pem --key /path/to/private-key.pem --database
vcli certificate add mycert --cert /path/on/server/certificate.pem --key /path/on/server/private-key.pem --disk
vcli certificate add mycert --cert /path/to/concatenated.pem --database
vcli certificate update 1 --cert /path/to/certificate.pem --key /path/to/private-key.pem --database
vcli certificate update 1 --cert /path/on/server/certificate.pem --key /path/on/server/private-key.pem --disk
vcli certificate update 1 --cert /path/to/concatenated.pem --database
vcli certificate update 1 --name newname
vcli certificate delete 1
vcli certificate inspect 1
Options for certificate storage:
–database/–disk are options that determine where and how the certificates are stored and managed.
–database Option:
Certificate and key will be stored in the database. Once stored,
users can't directly access the certificate and private key; only the certificate context
with details like expiration dates, SANs and configuration is available.
–disk Option:
Only the certificate and key paths are stored in the database.
During deployment, the agent or router will search for the certificate
at the specified absolute path, which the component needs access to.
This approach is more passive, as the controller will not retrieve
the certificate content, and therefore, it will not have access
to the certificate context, including details such as Expiry, SANs, etc.
In vcli, all certificate fields will be displayed as "Unmanaged."
Any changes made to the certificate source on disk will be recognized
by the agent or router. The updated certificate will be used
immediately for incoming connections.
-h, --help help for certificates
-c, --config string configuration file for the CLI (default ~/.vcli.yml)
Could also be set via VARNISH_CONTROLLER_CLI_CONFIG=/path/to/config.yml
--csv Output the response table as CSV format.
-j, --json Output the response table as JSON format.