|
1 | 1 | .\" generated with Ronn/v0.7.3 |
2 | 2 | .\" http://github.com/rtomayko/ronn/tree/0.7.3 |
3 | 3 | . |
4 | | -.TH "PUPPETCONF" "5" "May 2023" "Puppet, Inc." "Puppet manual" |
| 4 | +.TH "PUPPETCONF" "5" "June 2023" "Puppet, Inc." "Puppet manual" |
5 | 5 | \fBThis page is autogenerated; any changes will get overwritten\fR |
6 | 6 | . |
7 | 7 | .SH "Configuration settings" |
@@ -163,6 +163,20 @@ The port to use for the certificate authority\. |
163 | 163 | . |
164 | 164 | .IP "" 0 |
165 | 165 | . |
| 166 | +.SS "ca_refresh_interval" |
| 167 | +How often the Puppet agent refreshes its local CA certs\. By default the CA certs are refreshed once every 24 hours\. If a different duration is specified, then the agent will refresh its CA certs whenever it next runs and the elapsed time since the certs were last refreshed exceeds the duration\. |
| 168 | +. |
| 169 | +.P |
| 170 | +In general, the duration should be greater than the \fBruninterval\fR\. Setting it to 0 or an equal or lesser value than \fBruninterval\fR, will cause the CA certs to be refreshed on every run\. |
| 171 | +. |
| 172 | +.P |
| 173 | +If the agent downloads new CA certs, the agent will use it for subsequent network requests\. If the refresh request fails or if the CA certs are unchanged on the server, then the agent run will continue using the local CA certs it already has\. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y)\. |
| 174 | +. |
| 175 | +.IP "\(bu" 4 |
| 176 | +\fIDefault\fR: \fB1d\fR |
| 177 | +. |
| 178 | +.IP "" 0 |
| 179 | +. |
166 | 180 | .SS "ca_server" |
167 | 181 | The server to use for certificate authority requests\. It\'s a separate server because it cannot and does not need to horizontally scale\. |
168 | 182 | . |
@@ -395,7 +409,7 @@ Prints the value of a specific configuration setting\. If the name of a setting |
395 | 409 | How often the Puppet agent refreshes its local CRL\. By default the CRL is refreshed once every 24 hours\. If a different duration is specified, then the agent will refresh its CRL whenever it next runs and the elapsed time since the CRL was last refreshed exceeds the duration\. |
396 | 410 | . |
397 | 411 | .P |
398 | | -In general, the duration should be greater than the \fBruninterval\fR\. Setting it to an equal or lesser value will cause the CRL to be refreshed on every run\. |
| 412 | +In general, the duration should be greater than the \fBruninterval\fR\. Setting it to 0 or an equal or lesser value than \fBruninterval\fR, will cause the CRL to be refreshed on every run\. |
399 | 413 | . |
400 | 414 | .P |
401 | 415 | If the agent downloads a new CRL, the agent will use it for subsequent network requests\. If the refresh request fails or if the CRL is unchanged on the server, then the agent run will continue using the local CRL it already has\.This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y)\. |
|
0 commit comments