@@ -77,7 +77,21 @@ As with recent milestones, M17 does not contain any in-place schema changes (no
...
@@ -77,7 +77,21 @@ As with recent milestones, M17 does not contain any in-place schema changes (no
### GCZ (Geospatial Consumption Zone)
### GCZ (Geospatial Consumption Zone)
- To add
In an effort to align the GCZ project's structure more closely with other OSDU Core / DDMS services, we have updated the structure of the Geospatial Consumption Zone repository ([see PR](https://community.opengroup.org/osdu/platform/consumption/geospatial/-/merge_requests/90)).
### Structural Changes
*`osdu_gcz_transformer` directory is now `gcz-transformer`
*`osdu_gcz_provider` directory is now `gcz-provider`
*`osdu_gcz_test_assets` directory is now `gcz-test-assets`
*`osdu_gcz_wiki` directory is now `gcz-docs`
* Contents of the root `assets` folder have been relocated to `gcz-docs/assets`
* Root `ignite` folder and `osdu_gcz_transformer/ignite` folder have been removed from the repository
* These were GCZ byproducts and are not relevant to new consumers
* Transformer `src` code has been relocated to `gcz-transformer/gcz-transformer-core`
* Provider `src` code has been relocated to `gcz-provider/gcz-provider-core`
*`devops` and `provider` directories have been added to both `gcz-transformer` and `gcz-provider` directories with subdirectories for CSPs to extend upon or provide their own documentation and deployment strategies relevant to their specific environments (foundation to support SPI model for thin, CSP-specific extensions of the core code)
* Transformer config files (`application-local.yml`, `application-remote.yml`, and `application-k8s-remote.yml`) have been merged into a singular `application.yml` file and that file has been relocated into the `gcz-transformer/.config` directory
* Provider config file `koop-config.json` has been relocated into the `gcz-provider/.config` directory