Update home authored by Daniel Perna's avatar Daniel Perna
......@@ -414,11 +414,7 @@ From **2022-present** the following have been true, both in the CSP-oriented dep
In **2024-2025 (M25)**, the following was **_also_** true for the **Azure** implementation:
* A configuration flag _bypassed_ both the Dataset schema and Dataset Service to write direct to the CSP BLOB storage. This is in the same cluster as the rest of the OSDU deployment, but the RAFS DDMS set up its own "bucket". Credentials came from the OSDU Partition Service. (This is the same approach as the Wellbore DDMS, as of March 2025.) This variation was partially due to performance, and partially due to DDMS architectural principles (i.e., that DDMS content should only be accessible via the DDMS).
**Post-2025** in order to uphold the principle that DDMS content should only be accessible via the DDMS (not through Dataset catalog schemas), it is possible that the RAFS DDMS will not use a Dataset record, but will still use an appropriate OSDU core service (e.g. Dataset Service, File DDMS). Stay tuned.
* A configuration flag _bypassed_ both the Dataset schema and Dataset Service to write direct to the CSP BLOB storage. This is in the same cluster as the rest of the OSDU deployment, but the RAFS DDMS set up its own "bucket". Credentials came from the OSDU Partition Service. (This was the same approach as the Wellbore DDMS, as of March 2025.) This variation was partially due to performance, and partially due to DDMS architectural principles (i.e., that DDMS content should only be accessible via the DDMS).
### 14. For OSDU M25 (March 2025), the RAFS DDMS has an endpoint called "dev-samplesanalysis". What is this, and how does it relate to the main "samplesanalysis" (v2) endpoint?
......
......