m16 MR's:
This reverts merge request !691
Copy of !701
Making helm changes to configure the docker image property added and tested along MR: infra-azure-provisioning!889
Partition MR changeset: osdu/platform/system/partition!473
Need the variable to be passed as env variable for the check to be functional in above MR.
Have tested in one-box in the above linked MR.
m16 PR: Partition ddp change (!449)
Modified the partition-service core-package to configure permission check for CRUD operations explicitly. A new overridden method is added for implementation to fulfill the requirements. The default flow for non-azure implementations remains the same logic wise.
There is a new configuration variable {enable.crud.based.authorization} added to enable the check before accepting any rest API call within preauthorize annotation.
If the above flag is enabled by ISP, the Create/Patch/Delete calls will be forbidden on security-token generated using all the non-customer apps. Only the tokens with customer appid's are allowed to perform CRUD operations.
Testing for partition changes
Before Changes:
Using non MSI token: GET allowed: LIST allowed: CREATE allowed: DELETE allowed: PATCH allowed:
After Changes:
GET allowed: LIST allowed: CREATE not allowed: PATCH not allowed: DELETE not allowed
GET allowed. CREATE allowed. LIST allowed. DELETE allowed. PATCH allowed.
Currently the deployment job initializes partition and entitlements. With this change extending its functionality to be capable to remove partition data. Will be extending it further to be able to delete entitlements in the future.
Original MR: Upgrading deployment job by adding partition removing capability. (!889)
Current MR: Revert "Merge branch 'revert-c5217c27' into 'azure/m16-master'" (!899) · Merge requests · Open Subsurface Data Universe Software / Platform / Deployment and Operations / infra-azure-provisioning · GitLab (opengroup.org)
Duplicate dag file in Manifest Ingestion Dag folder, causing failures in Dags DataSeeding.
DDMS backend service to send back null response when CORS enabled. This is to ensure CORS at virtual service layer is honored.
I see these pipelines are already failing and tracked by M14 crew. cc: @sumrazafar @PrashanthK
@vineethguna I see that the pipelines have failed, is there any further merges needed
@chad not sure if this is still relevant to be open. This is confirmed as fixed. can you please close this?
Release name: M12
The following steps must be completed OSDU Azure release.
For more information, visit our release documentation here.
Infra Board closure
Deploy terraform scripts
Create service release images
Create Data seeding
Upload Data prior to service deployment
Service deployment (Install Charts to ACR)
Upload Data post to service deployment
Load community provided datasets post to service deployment
Validation
Test services and dags using REST scriptsLink.
Add Smoke Tests for services for M12 using Postman
Preshipping community require test collections for validation which are placed here Link.
Need to enhance these test at par with our probe tests and any new development since M8 release.
Internal Probe Tests location for reference Link
Platform Validation Tests for reference Link
Related to #207.
Release name: M10
The following steps must be completed OSDU Azure release.
For more information, visit our release documentation here.
Infra Board closure
Deploy terraform scripts
Create service release images
Create Data seeding
Upload Data prior to service deployment
Service deployment
Upload Data post to service deployment
Load community provided datasets post to service deployment
Validation
Test services and dags using REST scriptsLink.
Add Smoke Tests for services for M10 using Postman
Community require test collections for validation which are placed here Link.
Need to enhance these test at par with our probe tests and any new development since M8 release.
Internal Probe Tests location for reference Link
Platform Validation Tests for reference Link
Thanks @ChrisZhang for logging this placeholder.