update to DD schema repo SHA 8b96be9fb00a80374db4ab9129db16f68e9c8e11 2022-07-22
Closes #110 (closed)
M13 Details
DD schema repo SHA 8b96be9fb00a80374db4ab9129db16f68e9c8e11, 2022-07-22
New schemas (Domain Owner)
dataset group-type
- ConnectedSource.Generic.1.0.0.json (EDS)
master-data group-type
- ConnectedSourceDataJob.1.0.0.json (EDS)
- ConnectedSourceRegistryEntry.1.0.0.json (EDS)
- PerforationInterval.1.0.0.json (Well-Taxonomy)
- PerforationJob.1.0.0.json (Well-Taxonomy)
- SeismicProcessingProject.1.2.0.json (Seismic)
reference-data group-type
- AnnularFluidType.1.0.0.json (Well-Taxonomy)
- BitType.1.0.1.json (PPDM)
- BottomHolePressureType.1.0.0.json (Well-Taxonomy)
- OAuth2FlowType.1.0.0.json (EDS)
- PerforationCentralizationMethodType.1.0.0.json (Well-Taxonomy)
- PerforationConveyedMethod.1.0.0.json (Well-Taxonomy)
- PerforationGunCarrierCategory.1.0.0.json (Well-Taxonomy)
- PerforationGunCarrierModel.1.0.0.json (Well-Taxonomy)
- PerforationGunCarrierType.1.0.0.json (Well-Taxonomy)
- PerforationGunChargeShape.1.0.0.json (Well-Taxonomy)
- PerforationGunChargeSize.1.0.0.json (Well-Taxonomy)
- PerforationGunChargeType.1.0.0.json (Well-Taxonomy)
- PerforationGunFiringHeadType.1.0.0.json (Well-Taxonomy)
- PerforationGunMetallurgyType.1.0.0.json (Well-Taxonomy)
- PerforationGunPhasingType.1.0.0.json (Well-Taxonomy)
- PerforationIntervalReason.1.0.0.json (Well-Taxonomy)
- PerforationIntervalType.1.0.0.json (Well-Taxonomy)
- PerforationIntervalWLSize.1.0.0.json (Well-Taxonomy)
- PerforationPillType.1.0.0.json (Well-Taxonomy)
- SecuritySchemeType.1.0.0.json (EDS)
- SeismicMigrationType.1.0.1.json (PPDM)
- SeismicPickingType.1.0.1.json (PPDM)
- SeismicWaveType.1.0.1.json (PPDM)
- VerticalMeasurementType.1.0.1.json (PPDM)
work-product-component group-type
- FaultSystem.1.2.0.json (Seismic)
- SeismicTraceData.1.2.0.json (Seismic)
- VelocityModeling.1.1.0.json (Seismic)
Updated Schema Registration Resource
- load_sequence.1.0.0.json
Merge request reports
Activity
changed milestone to %M13 - Release 0.16
requested review from @pbehede and @akumar290
assigned to @gehrmann
@shrikgar can you please check why IBM bootstrapping is failing here?
@ashwani_pandey please chk IBM pipeline
@pbehede Its passing now
Anyone from Azure team looking into this? Hopefully we can catch this early if there are any issues. @gehrmann
@chad @gehrmann : Azure gitlab environment has been unstable from past few months. Deployment occasionally fails with 502 either during bootstrap or IT.
In my opinion we can proceed with this PR since it is not related to a code change and just addition of new schemas. But, we must raise this raise this with Azure team for a longterm fix.
@yaraslau_sushchyk Please help check on this. Otherwise as @akumar290 mentioned, we can proceed to merge this.
Edited by Chad Leongadded 19 commits
-
5949c73c...e0ddee94 - 18 commits from branch
master
- 22f5200c - Merge remote-tracking branch 'origin/master' into 110-osdu-dd-m13-delivery
-
5949c73c...e0ddee94 - 18 commits from branch
- Resolved by Paresh Behede
Pipelines have passed. Can we merge this? @akumar290 @pbehede @gehrmann
mentioned in commit f6e6102f