You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
t.Skip("set ARK_LIVE_TEST=true to run this test against the live service")
38
+
return
39
+
}
35
40
arktesting.SkipIfNoEnv(t)
36
41
37
42
t.Log("This test runs against a live service and has been known to flake. If you see timeout issues it's possible that the test is flaking and it could be unrelated to your changes.")
This will set the replicaset count more information can be found here: https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/
94
+
#### **acceptTerms** ~ `bool`
95
+
> Default value:
96
+
> ```yaml
97
+
> false
98
+
> ```
99
+
100
+
Must be set to indicate that you have read and accepted the CyberArk Terms of Service. If false, the helm chart will fail to install and will print a message with instructions on how to accept the TOS.
94
101
#### **image.repository** ~ `string`
95
102
> Default value:
96
103
> ```yaml
@@ -298,10 +305,11 @@ This description will be associated with the data that the agent uploads to the
298
305
#### **config.sendSecretValues** ~ `bool`
299
306
> Default value:
300
307
> ```yaml
301
-
> false
308
+
> true
302
309
> ```
303
310
304
-
Enable sending of Secret values to CyberArk in addition to metadata. Metadata is always sent, but the actual values of Secrets are not sent by default. When enabled, Secret data is encrypted using envelope encryption using a key managed by CyberArk. Default: false (but default will change to true for a future release)
311
+
Enable sending of Secret values to CyberArk in addition to metadata. Metadata is always sent, but the actual values of Secrets are not sent by default. When enabled, Secret data is encrypted using envelope encryption using a key managed by CyberArk, fetched from the Discovery and Context service.
Copy file name to clipboardExpand all lines: deploy/charts/disco-agent/templates/deployment.yaml
+3Lines changed: 3 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,6 @@
1
+
{{- if not .Values.acceptTerms }}
2
+
{{- fail "\n\n=================================================================\n Terms & Conditions Notice\n=================================================================\n\nBefore installing this application, you must review and accept\nthe terms and conditions available at:\nhttps://www.cyberark.com/contract-terms/\n\nTo proceed with installation, you must indicate acceptance by\nsetting:\n\n - In your values file: acceptTerms: true\n or\n - Via the Helm flag: --set acceptTerms=true\n\nBy continuing with the next command, you confirm that you have\nreviewed and accepted these terms and conditions.\n\n=================================================================\n" }}
Copy file name to clipboardExpand all lines: deploy/charts/disco-agent/values.schema.json
+10-2Lines changed: 10 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,9 @@
3
3
"helm-values": {
4
4
"additionalProperties": false,
5
5
"properties": {
6
+
"acceptTerms": {
7
+
"$ref": "#/$defs/helm-values.acceptTerms"
8
+
},
6
9
"affinity": {
7
10
"$ref": "#/$defs/helm-values.affinity"
8
11
},
@@ -84,6 +87,11 @@
84
87
},
85
88
"type": "object"
86
89
},
90
+
"helm-values.acceptTerms": {
91
+
"default": false,
92
+
"description": "Must be set to indicate that you have read and accepted the CyberArk Terms of Service. If false, the helm chart will fail to install and will print a message with instructions on how to accept the TOS.",
93
+
"type": "boolean"
94
+
},
87
95
"helm-values.affinity": {
88
96
"default": {},
89
97
"type": "object"
@@ -152,8 +160,8 @@
152
160
"type": "string"
153
161
},
154
162
"helm-values.config.sendSecretValues": {
155
-
"default": false,
156
-
"description": "Enable sending of Secret values to CyberArk in addition to metadata. Metadata is always sent, but the actual values of Secrets are not sent by default. When enabled, Secret data is encrypted using envelope encryption using a key managed by CyberArk. Default: false (but default will change to true for a future release)",
163
+
"default": true,
164
+
"description": "Enable sending of Secret values to CyberArk in addition to metadata. Metadata is always sent, but the actual values of Secrets are not sent by default. When enabled, Secret data is encrypted using envelope encryption using a key managed by CyberArk, fetched from the Discovery and Context service.\nDefault: true",
Copy file name to clipboardExpand all lines: deploy/charts/disco-agent/values.yaml
+6-3Lines changed: 6 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,9 @@
5
5
# This will set the replicaset count more information can be found here: https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/
6
6
replicaCount: 1
7
7
8
+
# Must be set to indicate that you have read and accepted the CyberArk Terms of Service. If false, the helm chart will fail to install and will print a message with instructions on how to accept the TOS.
9
+
acceptTerms: false
10
+
8
11
# This sets the container image more information can be found here: https://kubernetes.io/docs/concepts/containers/images/
9
12
image:
10
13
repository: ""
@@ -157,9 +160,9 @@ config:
157
160
# Enable sending of Secret values to CyberArk in addition to metadata.
158
161
# Metadata is always sent, but the actual values of Secrets are not sent by default.
159
162
# When enabled, Secret data is encrypted using envelope encryption using
160
-
# a key managed by CyberArk.
161
-
# Default: false (but default will change to true for a future release)
162
-
sendSecretValues: false
163
+
# a key managed by CyberArk, fetched from the Discovery and Context service.
t.Skip("set ARK_LIVE_TEST=true to run this test against the live service")
70
+
return
71
+
}
72
+
66
73
arktesting.SkipIfNoEnv(t)
67
74
68
75
t.Log("This test runs against a live service and has been known to flake. If you see timeout issues it's possible that the test is flaking and it could be unrelated to your changes.")
0 commit comments