|
2 | 2 |
|
3 | 3 | # Edit an Object Store Secret |
4 | 4 |
|
5 | | - |
6 | | - |
7 | | -> ### Note: |
8 | | -> For input artifacts only |
9 | | -> |
10 | | -> You can create multiple secrets using different values for `name`, but you must create a default first. |
11 | | -
|
12 | | -> ### Tip: |
13 | | -> The `pathPrefix` is useful if you share the same bucket for different projects. You can set the name of your project folder to `my-ml-project1`, for example. All data is then stored in that folder. |
14 | | -
|
15 | | -> ### Note: |
16 | | -> If the `AI-Resource-Group` header is not specified, the *<Resource Group\>* is assigned the value `"default"` automatically. |
17 | | -
|
18 | | -> ### Restriction: |
19 | | -> When using an SAP HANA Data Lake object store with output artifacts pointing to a directory, you cannot use `archive: none: {}` in your workflow templates to disable artifact archiving. For more information, see [Workflow Templates](workflow-templates-83523ab.md). |
20 | | -
|
21 | 5 | <a name="task_i3h_n13_tcc"/> |
22 | 6 |
|
23 | 7 | <!-- task\_i3h\_n13\_tcc --> |
@@ -151,12 +135,18 @@ Edit your object store secret details using the endpoint `$AI_API_URL/v2/admin/o |
151 | 135 | > |
152 | 136 | > You can create multiple secrets using different values for `name`, but you must create a default first. |
153 | 137 |
|
| 138 | +> ### Restriction: |
| 139 | +> Output artifacts can only use the default object store. |
| 140 | +
|
154 | 141 | > ### Tip: |
155 | 142 | > The `pathPrefix` is useful if you share the same bucket for different projects. You can set the name of your project folder to `my-ml-project1`, for example. All data is then stored in that folder. |
156 | 143 |
|
157 | 144 | > ### Note: |
158 | 145 | > If the `AI-Resource-Group` header is not specified, the *<Resource Group\>* is assigned the value `"default"` automatically. |
159 | 146 |
|
| 147 | +> ### Restriction: |
| 148 | +> When using an SAP HANA Data Lake object store with output artifacts pointing to a directory, you cannot use `archive: none: {}` in your workflow templates to disable artifact archiving. For more information, see [Workflow Templates](workflow-templates-83523ab.md). |
| 149 | +
|
160 | 150 | <a name="task_cxf_n13_tcc"/> |
161 | 151 |
|
162 | 152 | <!-- task\_cxf\_n13\_tcc --> |
@@ -269,17 +259,23 @@ SAP AI Core supports multiple hyperscaler object stores, including the following |
269 | 259 | ``` |
270 | 260 |
|
271 | 261 |
|
272 | | -3. Send the request. |
273 | | -
|
274 | 262 | > ### Note: |
275 | 263 | > For input artifacts only |
276 | 264 | > |
277 | 265 | > You can create multiple secrets using different values for `name`, but you must create a default first. |
278 | 266 |
|
| 267 | + > ### Restriction: |
| 268 | + > Output artifacts can only use the default object store. |
| 269 | +
|
279 | 270 | > ### Tip: |
280 | 271 | > The `pathPrefix` is useful if you share the same bucket for different projects. You can set the name of your project folder to `my-ml-project1`, for example. All data is then stored in that folder. |
281 | 272 |
|
282 | 273 | > ### Note: |
283 | 274 | > If the `AI-Resource-Group` header is not specified, the *<Resource Group\>* is assigned the value `"default"` automatically. |
284 | 275 |
|
| 276 | + > ### Restriction: |
| 277 | + > When using an SAP HANA Data Lake object store with output artifacts pointing to a directory, you cannot use `archive: none: {}` in your workflow templates to disable artifact archiving. For more information, see [Workflow Templates](workflow-templates-83523ab.md). |
| 278 | +
|
| 279 | +3. Send the request. |
| 280 | +
|
285 | 281 |
|
0 commit comments