Skip to content

Commit

Permalink
feat: add changelogs for latest changes
Browse files Browse the repository at this point in the history
  • Loading branch information
buehner committed Oct 16, 2024
1 parent 8cf44a3 commit dd63a00
Show file tree
Hide file tree
Showing 3 changed files with 71 additions and 0 deletions.
40 changes: 40 additions & 0 deletions charts/geoserver/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
# 6.0.0 (2024-10-15)

### Features

* if `geofence.enableInitScript` is true, the `init-geofence` initContainer will also care about the existence of the geofence database (configured in `geofence.databaseName`), so the database will be created, if it does not yet exist. This is helpful for initial/vanilla deployments.

### BREAKING CHANGES

* The field `geofence.dataSourceUrl` has been removed and is replaced by 3 new value fields:
* `geofence.databaseHost`
* `geofence.databasePort`
* `geofence.databaseName`

You only have to adjust your project/deployment specific `values.yaml` if you were overwriting `geofence.dataSourceUrl` there before. In that case you have to migrate the info that was contained in `geofence.dataSourceUrl` to the 3 new fields.

See [here](https://github.com/terrestris/helm-charts/commit/a4f3168d9d74f5e4638bd2220f81c25c6be6f172).


# 5.0.0 (2024-10-11)

### Features

* default GeoServer version is now 2.26.0 (if not overwritten in the `image.repository` and/or `image.tag` values)

### BREAKING CHANGES

* The value `ingress.annotations.spec.ingressClassName` has been replaced by the new value `ingress.className`
* You have to adjust your project/deployment specific `values.yaml` if you were overwriting `ingress.annotations.spec.ingressClassName` there before. In that case you have to set the value in the new field `ingress.className` now.
* The `ingress.hosts.paths` (string) array is now an array of objects with the properties `path` and `pathType`.
* In case you have to adjust this in your `values.yaml`, here is an example:
* Before: `paths: [ "/mypath" ]`
* New:
```
paths:
- path: /mypath
pathType: ImplementationSpecific
```


See [here](https://github.com/terrestris/helm-charts/commit/c12cfb7a70e1f29e693abc4a880bb2422cbf1876).
18 changes: 18 additions & 0 deletions charts/mapfish-print/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
# 3.0.0 (2024-10-11)

### BREAKING CHANGES

* The value `ingress.annotations.spec.ingressClassName` has been replaced by the new value `ingress.className`
* You have to adjust your project/deployment specific `values.yaml` if you were overwriting `ingress.annotations.spec.ingressClassName` there before. In that case you have to set the value in the new field `ingress.className` now.
* The `ingress.hosts.paths` (string) array is now an array of objects with the properties `path` and `pathType`.
* In case you have to adjust this in your `values.yaml`, here is an example:
* Before: `paths: [ "/mypath" ]`
* New:
```
paths:
- path: /mypath
pathType: ImplementationSpecific
```


See [here](https://github.com/terrestris/helm-charts/commit/908b4d6e28fb0cfd0c9336f916af687e5814202b).
13 changes: 13 additions & 0 deletions charts/shogun/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
# 3.0.0 (2024-10-15)

### BREAKING CHANGES

* This version updates the dependent geoserver chart from version 5.0.0 to 6.0.0, so please have a look at the [geoserver chart changelog](../geoserver/CHANGELOG.md) for adjustments in your project specific `values.yaml` of your shogun deployment.


# 2.0.0 (2024-10-11)

### BREAKING CHANGES

* This version updates the dependent geoserver chart from version 4.x to 5.0.0, so please have a look at the [geoserver chart changelog](../geoserver/CHANGELOG.md) for adjustments in your project specific `values.yaml` of your shogun deployment.
* This version also updates the dependent mapfish-print chart from version 2.x to 3.0.0, so please have a look at the [mapfish-print chart changelog](../mapfish-print/CHANGELOG.md) for adjustments in your project specific `values.yaml` of your shogun deployment.

0 comments on commit dd63a00

Please sign in to comment.