Merge from M8-Azure to master to onboard wellbore to latest OSDU version
Overview
- Merge from M8-Azure to master to onboard wellbore to latest OSDU version
- Backlog item - 7096
Testing
- Pipelines green should be enough.
- Additional testing is not required since already going to perform postman collections test while making change in code sync in OAK.
Edited by Dmitriy Rudko
Merge request reports
Activity
requested review from @sumrazafar and @rising
assigned to @Vkamani
requested review from @Dmitriy_Rudko
added 1206 commits
-
18a6ad90...fb884f6a - 1205 commits from branch
master
- 759cc553 - Merge branch 'master' into 'Azure/OSDU-Wellbore-DDMS-M8-Master'
-
18a6ad90...fb884f6a - 1205 commits from branch
@Vkamani please take a look at the failing steps and steps with warnings. Because now we are merging into Master, we have to ensure that our changes are green.
When the pipeline will be green, we have to get at least 1 approval from another Cloud Provider / SLB.
What needs to be fixed:
- I see "yaml invalid" error with "osdu-gcp-dev2-test-python: unknown keys in
extends
(.osdu-gcp-dev2-variables)" message - Following Scans steps are failing with warnings:
- eslint-sast
- gemnasium-python-dependency
- Deployments steps are failing:
- aws-update-eks
- Tests are failing for all CPSs
- I see "yaml invalid" error with "osdu-gcp-dev2-test-python: unknown keys in
changed milestone to %M12 - Release 0.15
Please register or sign in to reply