seismic-dms-service merge requestshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests2023-11-07T14:08:08Zhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/989[Test Only] Check logs2023-11-07T14:08:08ZDiego Molteni[Test Only] Check logs## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [ ] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [ ] Yes
## Have you set the target Milestone?
- [ ] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [ ] Yes
## Updates description?
> Update this part with a description of your changeshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/988fix: fixed subproject acls2023-11-07T09:04:15ZDiego Moltenifix: fixed subproject acls## Type of change
- [x] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [x] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [ ] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [x] Yes
## Have you set the target Milestone?
- [ ] No
- [x] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [x] Yes
## Updates description?
> Fixed default subproject ACLs checkM22 - Release 0.25Diego MolteniDiego Moltenihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/987[For MSFT Team Review] Add ComputeSize background service - infrastructure2023-11-14T16:30:19ZIzabela Kulakowska[For MSFT Team Review] Add ComputeSize background service - infrastructure## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [ ] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [ ] Yes
## Have you set the target Milestone?
- [ ] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [ ] Yes
## Updates description?
This MR adds ComputeSizeRunner to the infrastructure (analogically to Bulk Delete service)Izabela KulakowskaIzabela Kulakowskahttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/986test: E2E tests for the compute size operation2023-12-14T15:23:06ZMaggie Salaktest: E2E tests for the compute size operation## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [x] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [x] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [ ] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [x] Yes
## Have you set the target Milestone?
- [x] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [x] Yes
## Updates description?
This MR can be merged only after https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/1004
is merged as we need the implementation with Dockerfile, then update the infrastructure in azure-helm-repo and then we can merge E2E tests.
This MR sets also the feature flag for POST_PROCESS_ON_DATASET_CLOSE to true by default on AzureM22 - Release 0.25https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/985test: updated dataset register random test2023-11-06T14:45:31ZPratiksha Shedgetest: updated dataset register random test## Type of change
* [ ] Bug Fix
* [ ] Feature
* [ ] Pipeline
* [x] Test
* [ ] Documentation
## Does this introduce a change in the core logic?
* [x] No
* [ ] Yes
## Does this introduce a change in the cloud provider implementation, i...## Type of change
* [ ] Bug Fix
* [ ] Feature
* [ ] Pipeline
* [x] Test
* [ ] Documentation
## Does this introduce a change in the core logic?
* [x] No
* [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
* [x] AWS
* [x] Anthos
* [x] Azure
* [x] GCP
* [x] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
* [ ] No
* [x] Yes
## Have you set the target Milestone?
* [ ] No
* [x] Yes
## Have you set the no-detached-pipeline label?
* [ ] No
* [x] Yes
## Updates description?
> Issue description-In [this MR](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/926) I see that the variables _seismic_default_admins_ and _seismic_default_viewers_ are set three times with different values, but they are used only once and tests don't fail when the value changes. The logic of tests needs to be reviewed.
>
> Solution- The request body used for registering the dataset 'random' with variables 'seismic_default_admins' and 'seismic_default_viewer' was found to be unacceptable for that endpoint. I have since modified the endpoint's request body, and I can confirm that it is now working fine.M22 - Release 0.25https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/984[For MSFT Team Review]: Add `or` operator2023-11-09T09:59:40ZLaura Damian[For MSFT Team Review]: Add `or` operator[Internal PR, target branch is not `master`]
## Updates description?
> Support for 'not' operator
## How to test
Test with the http://localhost:5000/seistore-svc/api/v3/swagger-ui.html/#/Dataset/dataset-list-post.
The example body can ...[Internal PR, target branch is not `master`]
## Updates description?
> Support for 'not' operator
## How to test
Test with the http://localhost:5000/seistore-svc/api/v3/swagger-ui.html/#/Dataset/dataset-list-post.
The example body can be tweaked.
1. Make sure that there are datasets with name beginning with "W" that contain tagA or tagB or both are returned.
{
"search": "name=W%",
"select": "[name, path, created_by, gtags]",
"filter": {
"or": [{
"property": "gtags",
"operator": "CONTAINS",
"value": "tagA"
},
{
"property": "gtags",
"operator": "CONTAINS",
"value": "tagB"
}]
}
}
You can try other combinations.Laura DamianLaura Damianhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/983fix: update docker file to multistage docker build2023-11-02T21:37:13ZVaibhavi Kamanifix: update docker file to multistage docker build## Type of change
- [x] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [x] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [x] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [x] Yes
## Have you set the target Milestone?
- [x] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [x] No
- [ ] Yes
## Updates description?
> Adding Romica's [change](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/commit/68a4ce0e938770ad7914cd03cf963c080536c835) back from m16 branch to update docker file to multistage docker buildhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/982Removing AppInsights and Adding Swagger2023-12-04T20:10:47ZSumra ZafarRemoving AppInsights and Adding Swagger## Type of change
- [x] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [x] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [x] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [x] Yes
## Have you set the target Milestone?
- [ ] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [ ] Yes
## Updates description?
> Update this part with a description of your changeshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/981[For MSFT Team Review] Add dataset locking when updating compute_size2023-11-14T16:23:38ZIzabela Kulakowska[For MSFT Team Review] Add dataset locking when updating compute_size## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [ ] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [ ] Yes
## Have you set the target Milestone?
- [ ] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [ ] Yes
## Updates description?
Locking the dataset metadata when updating the compute size.
The implementation is doing 5 attempts to lock/unlock (the same way it's implemented in bulk delete).Izabela KulakowskaIzabela Kulakowskahttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/980Draft: Azure SDMS stable2023-11-02T06:22:09ZSumra ZafarDraft: Azure SDMS stable## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [ ] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [ ] Yes
## Have you set the target Milestone?
- [ ] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [ ] Yes
## Updates description?
> Update this part with a description of your changeshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/979test: Changes made to add Seismic file metadata unit tests to Service IT pipe...2023-11-01T22:46:56ZVaibhavi Kamanitest: Changes made to add Seismic file metadata unit tests to Service IT pipeline## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [x] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [x] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [x] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [x] Yes
## Have you set the target Milestone?
- [ ] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [x] No
- [ ] Yes
## Updates description?
> Changes made to add Seismic file metadata unit tests to Service IT pipeline and make it compatible with ADO.Vaibhavi KamaniVaibhavi Kamanihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/978[For MSFT Team Review]: Trigger compute size operation on dataset close2023-11-03T10:36:46ZMaggie Salak[For MSFT Team Review]: Trigger compute size operation on dataset close## Type of change
- [ ] Bug Fix
- [x] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [ ] Bug Fix
- [x] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [x] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [x] Yes
## Have you set the target Milestone?
- [x] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [x] No
- [ ] Yes
## Updates description?
This MR adds a trigger to re-compute the size of a dataset after it was closed.
As per the [ADR](https://dev.azure.com/ms-slb-cobuild/Zenith/_git/Smart%20Data%20Management/pullrequest/425?_a=files&path=/adrs/2023-09-29-compute-dataset-size.md), the trigger was added to the dataset `PATCH` endpoint, in case dataset is being closed with or without an update to its metadata.
Computing the size of the dataset is an operation executed asynchronously in a separate component which will be added as part of a separate MR. The trigger creates a queue message and pushes into onto a Redis queue, where it can be picked up by the separate service.
How to test this MR?
- Run SDMS locally and register a new dataset.
- Close the dataset, by calling the `PATCH` endpoint and pass the `sbit` value of the dataset (returned when dataset is registered) in the `close` parameter. The body can be left empty.
![image](/uploads/981efbb1641378176d5a4d0f2ec308d7/image.png)
- In order to see the message, connect to the configured `queueOperations` Redis instance in a client of your choice.Maggie SalakMaggie Salakhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/976feat: enable sidecar application insights in sdms sidecar2023-11-22T14:57:38ZJason Wangfeat: enable sidecar application insights in sdms sidecar## Type of change
- [ ] Bug Fix
- [x] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [ ] Bug Fix
- [x] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [x] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [x] Yes
## Have you set the target Milestone?
- [ ] No
- [x] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [x] Yes
## Updates description?
> Update this part with a description of your changesM22 - Release 0.25Diego MolteniJason WangDiego Moltenihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/975[For MSFT Team Review] Compute Size background service2023-11-06T15:37:00ZIzabela Kulakowska[For MSFT Team Review] Compute Size background service## Type of change
- [ ] Bug Fix
- [x] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [ ] Bug Fix
- [x] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [x] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [ ] Yes
## Have you set the target Milestone?
- [ ] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [ ] Yes
## Updates description?
This MR introduces a background service for computing dataset sizes.
It fetches the messages from the Redis queue and processes them:
- retrieves blob sizes and calculates the dataset size
- if the size changed executes a partial update CosmosDB metadata store for the dataset
Plese not it's an MR for internal review for MSFT team.
Locking the dataset for write will be added in the next MR.Izabela KulakowskaIzabela Kulakowskahttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/974fix: fixed bug on ls subprojects2023-11-06T15:11:37ZDiego Moltenifix: fixed bug on ls subprojects## Type of change
- [x] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [x] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [ ] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [x] Yes
## Have you set the target Milestone?
- [ ] No
- [x] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [x] Yes
## Updates description?
> Fixed a bug on the subproject ls endpointM22 - Release 0.25Diego MolteniDiego Moltenihttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/973[TEST] Msft/feat/e2e tests bulk deletion2023-10-31T09:10:41ZLaura Damian[TEST] Msft/feat/e2e tests bulk deletion## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [ ] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [ ] Yes
## Have you set the target Milestone?
- [ ] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [ ] Yes
## Updates description?
> Update this part with a description of your changeshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/972[For MSFT Team Review] add "not" operator2023-11-01T12:09:31ZLaura Damian[For MSFT Team Review] add "not" operator[Internal PR, target branch is not `master`]
## Updates description?
> Support for 'not' operator
## How to test
Test with the http://localhost:5000/seistore-svc/api/v3/swagger-ui.html/#/Dataset/dataset-list-post.
The example body can ...[Internal PR, target branch is not `master`]
## Updates description?
> Support for 'not' operator
## How to test
Test with the http://localhost:5000/seistore-svc/api/v3/swagger-ui.html/#/Dataset/dataset-list-post.
The example body can be tweaked.
1. Make sure that there are datasets with name beginning with "W" tagA and these are not returned.
{
"search": "name=W%",
"select": "[name, path, created_by, gtags]",
"filter": {
"not": {
"property": "gtags",
"operator": "CONTAINS",
"value": "tagA"
}
}
}
2. Make sure that there are datasets with name benginning with "W" and the following tags:
[tagA], [tagB], [tagA, tagB], [tagB, tagC], tagB.
The following payload should return datasets that contain [tagB], tagB, and [tagB, tagC].
{
"search": "name=W%",
"select": "[name, path, created_by, gtags]",
"filter": {
"and": [
{
"property": "gtags",
"operator": "CONTAINS",
"value": "tagB"
},
{
"property": "name",
"operator": "LIKE",
"value": "W%"
},
{
"not": {
"property": "gtags",
"operator": "CONTAINS",
"value": "tagA"
}
}
]
}
}
Please be aware that using limit does not work with the Sidecar at the moment (this is tracked).https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/971feat: add e2e tests for bulk-delete operation2023-10-31T09:53:43ZLaura Damianfeat: add e2e tests for bulk-delete operation## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [x] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [x] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [x] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [ ] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [x] Yes
## Have you set the target Milestone?
- [ ] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [x] Yes
## Updates description?
This PR brings in the end to end tests for the [newly introduced hierarchical bulk deletion](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/891).
This supersedes [MR 902](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/902)M22 - Release 0.25Laura DamianLaura Damianhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/970Draft: Testing DO NOT MERGE2023-10-30T15:59:28ZSumra ZafarDraft: Testing DO NOT MERGE## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [ ] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [ ] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [ ] Yes
## Have you set the target Milestone?
- [ ] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [ ] Yes
## Updates description?
> Update this part with a description of your changeshttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/merge_requests/969Dacarpen/vulnerability fixes2023-10-26T21:13:08ZDaniel CarpenterDacarpen/vulnerability fixes## Type of change
- [X] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [X] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if ...## Type of change
- [X] Bug Fix
- [ ] Feature
- [ ] Pipeline
- [ ] Test
- [ ] Documentation
## Does this introduce a change in the core logic?
- [X] No
- [ ] Yes
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Anthos
- [X] Azure
- [ ] GCP
- [ ] IBM
## Does this follow [conventional commits spec](https://www.conventionalcommits.org/en/v1.0.0/#summary)?
- [ ] No
- [ ] Yes
## Have you set the target Milestone?
- [ ] No
- [ ] Yes
## Have you set the no-detached-pipeline label?
- [ ] No
- [ ] Yes
## Updates description?
Update dockerfile to avoid including vulnerabilities in created image by using a multi-stage build
@rojunejaDaniel CarpenterDaniel Carpenter