update: source github.com/jsonnet-libs/k8s@488d5346

jsonnet-libs · Sep 27, 2023 · b4d53bd · b4d53bd
1 parent afa8800
commit b4d53bd
Show file tree

Hide file tree

Showing 8 changed files with 8 additions and 8 deletions.
diff --git a/0.1.0/_gen/secrets/v1beta1/vaultAuth.libsonnet b/0.1.0/_gen/secrets/v1beta1/vaultAuth.libsonnet
@@ -103,7 +103,7 @@
       '#withTokenExpirationSeconds':: d.fn(help='"TokenExpirationSeconds to set the ServiceAccount token."', args=[d.arg(name='tokenExpirationSeconds', type=d.T.integer)]),
       withTokenExpirationSeconds(tokenExpirationSeconds): { spec+: { kubernetes+: { tokenExpirationSeconds: tokenExpirationSeconds } } },
     },
-    '#storageEncryption':: d.obj(help="\"StorageEncryption provides the necessary configuration to encrypt the client storage cache. This should only be configured when client cache persistence with encryption is enabled. This is done by passing setting the manager's commandline argument --client-cache-persistence-model=direct-encrypted. Typically there should only ever be one VaultAuth configured with StorageEncryption in the Cluster, and it should have the label: cacheStorageEncryption=true\""),
+    '#storageEncryption':: d.obj(help="\"StorageEncryption provides the necessary configuration to encrypt the client storage cache. This should only be configured when client cache persistence with encryption is enabled. This is done by passing setting the manager's commandline argument --client-cache-persistence-model=direct-encrypted. Typically, there should only ever be one VaultAuth configured with StorageEncryption in the Cluster, and it should have the label: cacheStorageEncryption=true\""),
     storageEncryption: {
       '#withKeyName':: d.fn(help='"KeyName to use for encrypt/decrypt operations via Vault Transit."', args=[d.arg(name='keyName', type=d.T.string)]),
       withKeyName(keyName): { spec+: { storageEncryption+: { keyName: keyName } } },

diff --git a/0.1.0/_gen/secrets/v1beta1/vaultStaticSecret.libsonnet b/0.1.0/_gen/secrets/v1beta1/vaultStaticSecret.libsonnet
@@ -81,7 +81,7 @@
     withNamespace(namespace): { spec+: { namespace: namespace } },
     '#withPath':: d.fn(help='"Path of the secret in Vault, corresponds to the `path` parameter for, kv-v1: https://developer.hashicorp.com/vault/api-docs/secret/kv/kv-v1#read-secret kv-v2: https://developer.hashicorp.com/vault/api-docs/secret/kv/kv-v2#read-secret-version"', args=[d.arg(name='path', type=d.T.string)]),
     withPath(path): { spec+: { path: path } },
-    '#withRefreshAfter':: d.fn(help='"RefreshAfter a period of time, in duration notation"', args=[d.arg(name='refreshAfter', type=d.T.string)]),
+    '#withRefreshAfter':: d.fn(help='"RefreshAfter a period of time, in duration notation e.g. 30s, 1m, 24h"', args=[d.arg(name='refreshAfter', type=d.T.string)]),
     withRefreshAfter(refreshAfter): { spec+: { refreshAfter: refreshAfter } },
     '#withRolloutRestartTargets':: d.fn(help='"RolloutRestartTargets should be configured whenever the application(s) consuming the Vault secret does not support dynamically reloading a rotated secret. In that case one, or more RolloutRestartTarget(s) can be configured here. The Operator will trigger a \\"rollout-restart\\" for each target whenever the Vault secret changes between reconciliation events. All configured targets wil be ignored if HMACSecretData is set to false. See RolloutRestartTarget for more details."', args=[d.arg(name='rolloutRestartTargets', type=d.T.array)]),
     withRolloutRestartTargets(rolloutRestartTargets): { spec+: { rolloutRestartTargets: if std.isArray(v=rolloutRestartTargets) then rolloutRestartTargets else [rolloutRestartTargets] } },

diff --git a/0.2.0/_gen/secrets/v1beta1/vaultAuth.libsonnet b/0.2.0/_gen/secrets/v1beta1/vaultAuth.libsonnet
@@ -103,7 +103,7 @@
       '#withTokenExpirationSeconds':: d.fn(help='"TokenExpirationSeconds to set the ServiceAccount token."', args=[d.arg(name='tokenExpirationSeconds', type=d.T.integer)]),
       withTokenExpirationSeconds(tokenExpirationSeconds): { spec+: { kubernetes+: { tokenExpirationSeconds: tokenExpirationSeconds } } },
     },
-    '#storageEncryption':: d.obj(help="\"StorageEncryption provides the necessary configuration to encrypt the client storage cache. This should only be configured when client cache persistence with encryption is enabled. This is done by passing setting the manager's commandline argument --client-cache-persistence-model=direct-encrypted. Typically there should only ever be one VaultAuth configured with StorageEncryption in the Cluster, and it should have the label: cacheStorageEncryption=true\""),
+    '#storageEncryption':: d.obj(help="\"StorageEncryption provides the necessary configuration to encrypt the client storage cache. This should only be configured when client cache persistence with encryption is enabled. This is done by passing setting the manager's commandline argument --client-cache-persistence-model=direct-encrypted. Typically, there should only ever be one VaultAuth configured with StorageEncryption in the Cluster, and it should have the label: cacheStorageEncryption=true\""),
     storageEncryption: {
       '#withKeyName':: d.fn(help='"KeyName to use for encrypt/decrypt operations via Vault Transit."', args=[d.arg(name='keyName', type=d.T.string)]),
       withKeyName(keyName): { spec+: { storageEncryption+: { keyName: keyName } } },

diff --git a/0.2.0/_gen/secrets/v1beta1/vaultStaticSecret.libsonnet b/0.2.0/_gen/secrets/v1beta1/vaultStaticSecret.libsonnet
@@ -81,7 +81,7 @@
     withNamespace(namespace): { spec+: { namespace: namespace } },
     '#withPath':: d.fn(help='"Path of the secret in Vault, corresponds to the `path` parameter for, kv-v1: https://developer.hashicorp.com/vault/api-docs/secret/kv/kv-v1#read-secret kv-v2: https://developer.hashicorp.com/vault/api-docs/secret/kv/kv-v2#read-secret-version"', args=[d.arg(name='path', type=d.T.string)]),
     withPath(path): { spec+: { path: path } },
-    '#withRefreshAfter':: d.fn(help='"RefreshAfter a period of time, in duration notation"', args=[d.arg(name='refreshAfter', type=d.T.string)]),
+    '#withRefreshAfter':: d.fn(help='"RefreshAfter a period of time, in duration notation e.g. 30s, 1m, 24h"', args=[d.arg(name='refreshAfter', type=d.T.string)]),
     withRefreshAfter(refreshAfter): { spec+: { refreshAfter: refreshAfter } },
     '#withRolloutRestartTargets':: d.fn(help='"RolloutRestartTargets should be configured whenever the application(s) consuming the Vault secret does not support dynamically reloading a rotated secret. In that case one, or more RolloutRestartTarget(s) can be configured here. The Operator will trigger a \\"rollout-restart\\" for each target whenever the Vault secret changes between reconciliation events. All configured targets wil be ignored if HMACSecretData is set to false. See RolloutRestartTarget for more details."', args=[d.arg(name='rolloutRestartTargets', type=d.T.array)]),
     withRolloutRestartTargets(rolloutRestartTargets): { spec+: { rolloutRestartTargets: if std.isArray(v=rolloutRestartTargets) then rolloutRestartTargets else [rolloutRestartTargets] } },

diff --git a/docs/0.1.0/secrets/v1beta1/vaultAuth.md b/docs/0.1.0/secrets/v1beta1/vaultAuth.md
@@ -523,7 +523,7 @@ withTokenExpirationSeconds(tokenExpirationSeconds)
 
 ## obj spec.storageEncryption
 
-"StorageEncryption provides the necessary configuration to encrypt the client storage cache. This should only be configured when client cache persistence with encryption is enabled. This is done by passing setting the manager's commandline argument --client-cache-persistence-model=direct-encrypted. Typically there should only ever be one VaultAuth configured with StorageEncryption in the Cluster, and it should have the label: cacheStorageEncryption=true"
+"StorageEncryption provides the necessary configuration to encrypt the client storage cache. This should only be configured when client cache persistence with encryption is enabled. This is done by passing setting the manager's commandline argument --client-cache-persistence-model=direct-encrypted. Typically, there should only ever be one VaultAuth configured with StorageEncryption in the Cluster, and it should have the label: cacheStorageEncryption=true"
 
 ### fn spec.storageEncryption.withKeyName
 

diff --git a/docs/0.1.0/secrets/v1beta1/vaultStaticSecret.md b/docs/0.1.0/secrets/v1beta1/vaultStaticSecret.md
@@ -268,7 +268,7 @@ withPath(path)
 withRefreshAfter(refreshAfter)
 ```
 
-"RefreshAfter a period of time, in duration notation"
+"RefreshAfter a period of time, in duration notation e.g. 30s, 1m, 24h"
 
 ### fn spec.withRolloutRestartTargets
 

diff --git a/docs/0.2.0/secrets/v1beta1/vaultAuth.md b/docs/0.2.0/secrets/v1beta1/vaultAuth.md
@@ -523,7 +523,7 @@ withTokenExpirationSeconds(tokenExpirationSeconds)
 
 ## obj spec.storageEncryption
 
-"StorageEncryption provides the necessary configuration to encrypt the client storage cache. This should only be configured when client cache persistence with encryption is enabled. This is done by passing setting the manager's commandline argument --client-cache-persistence-model=direct-encrypted. Typically there should only ever be one VaultAuth configured with StorageEncryption in the Cluster, and it should have the label: cacheStorageEncryption=true"
+"StorageEncryption provides the necessary configuration to encrypt the client storage cache. This should only be configured when client cache persistence with encryption is enabled. This is done by passing setting the manager's commandline argument --client-cache-persistence-model=direct-encrypted. Typically, there should only ever be one VaultAuth configured with StorageEncryption in the Cluster, and it should have the label: cacheStorageEncryption=true"
 
 ### fn spec.storageEncryption.withKeyName
 

diff --git a/docs/0.2.0/secrets/v1beta1/vaultStaticSecret.md b/docs/0.2.0/secrets/v1beta1/vaultStaticSecret.md
@@ -268,7 +268,7 @@ withPath(path)
 withRefreshAfter(refreshAfter)
 ```
 
-"RefreshAfter a period of time, in duration notation"
+"RefreshAfter a period of time, in duration notation e.g. 30s, 1m, 24h"
 
 ### fn spec.withRolloutRestartTargets