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
Copy file name to clipboardExpand all lines: _docs/configure-ci-cd-pipeline/shared-configuration.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ You can create four types of shared configuration:
40
40
41
41
You can create as many shared snippets as you want (with unique names).
42
42
43
-
###Using external secrets as values.
43
+
###Using external secrets as values
44
44
45
45
Note that the default "shared secrets" and "secret yaml" entities use the built-in secret storage of Codefresh. You can also
46
46
use any[external secrets that you have defined]({{site.baseurl}}/docs/integrations/secret-storage/) (such as Kubernetes secrets), by using the normal entities and then clicking on the lock icon that appears.
Copy file name to clipboardExpand all lines: _docs/testing/test-reports.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,6 +109,12 @@ max-width="80%"
109
109
Then click*Save* to apply settings. You will use the name of the integration as an
110
110
environment variable in your Codefresh pipeline as explained in the next sections.
111
111
112
+
You can also
113
+
use any[external secrets that you have defined]({{site.baseurl}}/docs/integrations/secret-storage/) (such as Kubernetes secrets) as values by clicking on the lock icon that appears next to field.
114
+
115
+
If you have already specified the resource field during secret definition the just enter on the text field the name of the secret directly, i.e.`my-secret-key`.
116
+
If you didn't include a resource name during secret creation then enter the full name in the field like`my-secret-resource@my-secret-key`.
117
+
112
118
###Connecting Azure storage
113
119
114
120
For Azure, create a storage account as explained in the[documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-create) and find one of the[two access keys](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage) already created. Then once you have the storage account name and account key,
@@ -127,6 +133,12 @@ max-width="60%"
127
133
Then click*Save* to apply settings. You will use the name of the integration as an
128
134
environment variable in your Codefresh pipeline as explained in the next sections.
129
135
136
+
You can also
137
+
use any[external secrets that you have defined]({{site.baseurl}}/docs/integrations/secret-storage/) (such as Kubernetes secrets) as values by clicking on the lock icon that appears next to field.
138
+
139
+
If you have already specified the resource field during secret definition the just enter on the text field the name of the secret directly, i.e.`my-secret-key`.
140
+
If you didn't include a resource name during secret creation then enter the full name in the field like`my-secret-resource@my-secret-key`.
141
+
130
142
131
143
##Producing Allure test reports from Codefresh pipelines