update: source github.com/jsonnet-libs/k8s@81b00ffb

0.1.0/_gen/secrets/v1beta1/vaultDynamicSecret.libsonnet

@@ -130,6 +130,8 @@
     withParamsMixin(params): { spec+: { params+: params } },
     '#withPath':: d.fn(help="\"Path in Vault to get the credentials for, and is relative to Mount. Please consult https://developer.hashicorp.com/vault/docs/secrets if you are uncertain about what 'path' should be set to.\"", args=[d.arg(name='path', type=d.T.string)]),
     withPath(path): { spec+: { path: path } },
+    '#withRefreshAfter':: d.fn(help="\"RefreshAfter a period of time for VSO to sync the source secret data, in duration notation e.g. 30s, 1m, 24h. This value only needs to be set when syncing from a secret's engine that does not provide a lease TTL in its response. The value should be within the secret engine's configured ttl or max_ttl. The source secret's lease duration takes precedence over this configuration when it is greater than 0.\"", args=[d.arg(name='refreshAfter', type=d.T.string)]),
+    withRefreshAfter(refreshAfter): { spec+: { refreshAfter: refreshAfter } },
     '#withRenewalPercent':: d.fn(help='"RenewalPercent is the percent out of 100 of the lease duration when the lease is renewed. Defaults to 67 percent plus jitter."', args=[d.arg(name='renewalPercent', type=d.T.integer)]),
     withRenewalPercent(renewalPercent): { spec+: { renewalPercent: renewalPercent } },
     '#withRequestHTTPMethod':: d.fn(help='"RequestHTTPMethod to use when syncing Secrets from Vault. Setting a value here is not typically required. If left unset the Operator will make requests using the GET method. In the case where Params are specified the Operator will use the PUT method. Please consult https://developer.hashicorp.com/vault/docs/secrets if you are uncertain about what method to use. Of note, the Vault client treats PUT and POST as being equivalent. The underlying Vault client implementation will always use the PUT method."', args=[d.arg(name='requestHTTPMethod', type=d.T.string)]),

0.2.0/_gen/secrets/v1beta1/vaultDynamicSecret.libsonnet

@@ -130,6 +130,8 @@
     withParamsMixin(params): { spec+: { params+: params } },
     '#withPath':: d.fn(help="\"Path in Vault to get the credentials for, and is relative to Mount. Please consult https://developer.hashicorp.com/vault/docs/secrets if you are uncertain about what 'path' should be set to.\"", args=[d.arg(name='path', type=d.T.string)]),
     withPath(path): { spec+: { path: path } },
+    '#withRefreshAfter':: d.fn(help="\"RefreshAfter a period of time for VSO to sync the source secret data, in duration notation e.g. 30s, 1m, 24h. This value only needs to be set when syncing from a secret's engine that does not provide a lease TTL in its response. The value should be within the secret engine's configured ttl or max_ttl. The source secret's lease duration takes precedence over this configuration when it is greater than 0.\"", args=[d.arg(name='refreshAfter', type=d.T.string)]),
+    withRefreshAfter(refreshAfter): { spec+: { refreshAfter: refreshAfter } },
     '#withRenewalPercent':: d.fn(help='"RenewalPercent is the percent out of 100 of the lease duration when the lease is renewed. Defaults to 67 percent plus jitter."', args=[d.arg(name='renewalPercent', type=d.T.integer)]),
     withRenewalPercent(renewalPercent): { spec+: { renewalPercent: renewalPercent } },
     '#withRequestHTTPMethod':: d.fn(help='"RequestHTTPMethod to use when syncing Secrets from Vault. Setting a value here is not typically required. If left unset the Operator will make requests using the GET method. In the case where Params are specified the Operator will use the PUT method. Please consult https://developer.hashicorp.com/vault/docs/secrets if you are uncertain about what method to use. Of note, the Vault client treats PUT and POST as being equivalent. The underlying Vault client implementation will always use the PUT method."', args=[d.arg(name='requestHTTPMethod', type=d.T.string)]),

0.3.0/_gen/secrets/v1beta1/vaultDynamicSecret.libsonnet

@@ -130,6 +130,8 @@
     withParamsMixin(params): { spec+: { params+: params } },
     '#withPath':: d.fn(help="\"Path in Vault to get the credentials for, and is relative to Mount. Please consult https://developer.hashicorp.com/vault/docs/secrets if you are uncertain about what 'path' should be set to.\"", args=[d.arg(name='path', type=d.T.string)]),
     withPath(path): { spec+: { path: path } },
+    '#withRefreshAfter':: d.fn(help="\"RefreshAfter a period of time for VSO to sync the source secret data, in duration notation e.g. 30s, 1m, 24h. This value only needs to be set when syncing from a secret's engine that does not provide a lease TTL in its response. The value should be within the secret engine's configured ttl or max_ttl. The source secret's lease duration takes precedence over this configuration when it is greater than 0.\"", args=[d.arg(name='refreshAfter', type=d.T.string)]),
+    withRefreshAfter(refreshAfter): { spec+: { refreshAfter: refreshAfter } },
     '#withRenewalPercent':: d.fn(help='"RenewalPercent is the percent out of 100 of the lease duration when the lease is renewed. Defaults to 67 percent plus jitter."', args=[d.arg(name='renewalPercent', type=d.T.integer)]),
     withRenewalPercent(renewalPercent): { spec+: { renewalPercent: renewalPercent } },
     '#withRequestHTTPMethod':: d.fn(help='"RequestHTTPMethod to use when syncing Secrets from Vault. Setting a value here is not typically required. If left unset the Operator will make requests using the GET method. In the case where Params are specified the Operator will use the PUT method. Please consult https://developer.hashicorp.com/vault/docs/secrets if you are uncertain about what method to use. Of note, the Vault client treats PUT and POST as being equivalent. The underlying Vault client implementation will always use the PUT method."', args=[d.arg(name='requestHTTPMethod', type=d.T.string)]),

docs/0.1.0/secrets/v1beta1/vaultDynamicSecret.md

@@ -36,6 +36,7 @@ permalink: /0.1.0/secrets/v1beta1/vaultDynamicSecret/
   * [`fn withParams(params)`](#fn-specwithparams)
   * [`fn withParamsMixin(params)`](#fn-specwithparamsmixin)
   * [`fn withPath(path)`](#fn-specwithpath)
+  * [`fn withRefreshAfter(refreshAfter)`](#fn-specwithrefreshafter)
   * [`fn withRenewalPercent(renewalPercent)`](#fn-specwithrenewalpercent)
   * [`fn withRequestHTTPMethod(requestHTTPMethod)`](#fn-specwithrequesthttpmethod)
   * [`fn withRevoke(revoke)`](#fn-specwithrevoke)
@@ -303,6 +304,14 @@ withPath(path)
 
 "Path in Vault to get the credentials for, and is relative to Mount. Please consult https://developer.hashicorp.com/vault/docs/secrets if you are uncertain about what 'path' should be set to."
 
+### fn spec.withRefreshAfter
+
+```ts
+withRefreshAfter(refreshAfter)
+```
+
+"RefreshAfter a period of time for VSO to sync the source secret data, in duration notation e.g. 30s, 1m, 24h. This value only needs to be set when syncing from a secret's engine that does not provide a lease TTL in its response. The value should be within the secret engine's configured ttl or max_ttl. The source secret's lease duration takes precedence over this configuration when it is greater than 0."
+
 ### fn spec.withRenewalPercent
 
 ```ts

docs/0.2.0/secrets/v1beta1/vaultDynamicSecret.md

@@ -36,6 +36,7 @@ permalink: /0.2.0/secrets/v1beta1/vaultDynamicSecret/
   * [`fn withParams(params)`](#fn-specwithparams)
   * [`fn withParamsMixin(params)`](#fn-specwithparamsmixin)
   * [`fn withPath(path)`](#fn-specwithpath)
+  * [`fn withRefreshAfter(refreshAfter)`](#fn-specwithrefreshafter)
   * [`fn withRenewalPercent(renewalPercent)`](#fn-specwithrenewalpercent)
   * [`fn withRequestHTTPMethod(requestHTTPMethod)`](#fn-specwithrequesthttpmethod)
   * [`fn withRevoke(revoke)`](#fn-specwithrevoke)
@@ -303,6 +304,14 @@ withPath(path)
 
 "Path in Vault to get the credentials for, and is relative to Mount. Please consult https://developer.hashicorp.com/vault/docs/secrets if you are uncertain about what 'path' should be set to."
 
+### fn spec.withRefreshAfter
+
+```ts
+withRefreshAfter(refreshAfter)
+```
+
+"RefreshAfter a period of time for VSO to sync the source secret data, in duration notation e.g. 30s, 1m, 24h. This value only needs to be set when syncing from a secret's engine that does not provide a lease TTL in its response. The value should be within the secret engine's configured ttl or max_ttl. The source secret's lease duration takes precedence over this configuration when it is greater than 0."
+
 ### fn spec.withRenewalPercent
 
 ```ts

docs/0.3.0/secrets/v1beta1/vaultDynamicSecret.md

@@ -36,6 +36,7 @@ permalink: /0.3.0/secrets/v1beta1/vaultDynamicSecret/
   * [`fn withParams(params)`](#fn-specwithparams)
   * [`fn withParamsMixin(params)`](#fn-specwithparamsmixin)
   * [`fn withPath(path)`](#fn-specwithpath)
+  * [`fn withRefreshAfter(refreshAfter)`](#fn-specwithrefreshafter)
   * [`fn withRenewalPercent(renewalPercent)`](#fn-specwithrenewalpercent)
   * [`fn withRequestHTTPMethod(requestHTTPMethod)`](#fn-specwithrequesthttpmethod)
   * [`fn withRevoke(revoke)`](#fn-specwithrevoke)
@@ -303,6 +304,14 @@ withPath(path)
 
 "Path in Vault to get the credentials for, and is relative to Mount. Please consult https://developer.hashicorp.com/vault/docs/secrets if you are uncertain about what 'path' should be set to."
 
+### fn spec.withRefreshAfter
+
+```ts
+withRefreshAfter(refreshAfter)
+```
+
+"RefreshAfter a period of time for VSO to sync the source secret data, in duration notation e.g. 30s, 1m, 24h. This value only needs to be set when syncing from a secret's engine that does not provide a lease TTL in its response. The value should be within the secret engine's configured ttl or max_ttl. The source secret's lease duration takes precedence over this configuration when it is greater than 0."
+
 ### fn spec.withRenewalPercent
 
 ```ts