CRS reference values missing from GCP pre-ship R3 M13 environment when testing with V3 collections
Using https://community.opengroup.org/osdu/platform/testing/-/blob/master/Postman%20Collection/16_CICD_Setup_%20CRSCatalogServiceAPI/CRS%20Catalog%20Service%20API%20V3.skip_postman_collection.json https://community.opengroup.org/osdu/platform/testing/-/blob/master/Postman%20Collection/18_CICD_Setup_CRSConversionAPI/CRS%20Conversion%20Service%20V3.skip_postman_collection.json These are passing on AWS and Azure, but are failing on GCP because the reference values are not present.
Notes from Debasis email - (Drill down to FIXED, LOCAL, OPEN for exact JSON files)
https://community.opengroup.org/osdu/data/data-definitions/-/tree/master/ReferenceValues/Manifests/reference-data If the reference data is sourced from here, then we can get good coverage. Note to Dzmitry – It is not any collection. We request population of standard set of Reference Values from Data Definition team. In turn, that will help validation of CRS Catalog V3 and CRS Conversion V3 services.