|
1 | 1 | = Changelog
|
2 | 2 |
|
| 3 | +== Version 0.12.0 |
| 4 | +[cols="1,2,<10a", options="header"] |
| 5 | +|=== |
| 6 | +|ID|Type|Description |
| 7 | +|https://github.com/Axway-API-Management-Plus/apigw-maven-plugin/issues/35[#35] |
| 8 | +|Enhancement |
| 9 | +| Support removal of certificates. |
| 10 | + |
| 11 | +A new certificate type `empty` is introduced for the `update` object of the certificate configuration file. |
| 12 | +It indicates that a certificate will be updated with an empty certificate and therefore will be removed. |
| 13 | + |
| 14 | +[source,json] |
| 15 | +---- |
| 16 | +{ |
| 17 | + "certifictates": |
| 18 | + "to-be-deleted": { |
| 19 | + "origin": { |
| 20 | + "info": { |
| 21 | + "not_after": "2020-08-23T20:24:00+02:00", |
| 22 | + "subject": "CN=localhost, O=ACME Inc., C=EX" |
| 23 | + } |
| 24 | + }, |
| 25 | + "update": { |
| 26 | + "type": "empty" <1> |
| 27 | + } |
| 28 | + } |
| 29 | +} |
| 30 | +---- |
| 31 | +<1> Type `empty` will remove the certificate. |
| 32 | + |
| 33 | +|https://github.com/Axway-API-Management-Plus/apigw-maven-plugin/issues/36[#36] |
| 34 | +|Enhancement |
| 35 | +|The default source for new environmentalized fields is `property`. |
| 36 | + |
| 37 | +.Old default source |
| 38 | +[source,json] |
| 39 | +---- |
| 40 | +{ |
| 41 | + "field#0": { |
| 42 | + "source": "value", <1> |
| 43 | + "type": "string", |
| 44 | + "used": true, |
| 45 | + "value": null |
| 46 | + } |
| 47 | +} |
| 48 | +---- |
| 49 | +<1> Previously the default source for new fields is `value`. |
| 50 | + |
| 51 | +.New default source |
| 52 | +[source,json] |
| 53 | +---- |
| 54 | +{ |
| 55 | + "field#0": { |
| 56 | + "source": "property", <1> |
| 57 | + "type": "string", |
| 58 | + "used": true, |
| 59 | + "value": null |
| 60 | + } |
| 61 | +} |
| 62 | +---- |
| 63 | +<1> The new default source for new fields is `property`. |
| 64 | + |
| 65 | +[NOTE] |
| 66 | +==== |
| 67 | +In case of new environmentalized fields, the configuration file has to be edited to set the value for the new fields. |
| 68 | +
|
| 69 | +In case of the source of the value should be a property the name of the property has to be specified in the `value` attribute. |
| 70 | +Unfortunately it is easy to forget to also change the `source` attribute to `property`. |
| 71 | +As the default source is `value` the configuration tool will just configure the name of property instead of the content of the property, without any warning or error. |
| 72 | +
|
| 73 | +To prevent this pitfall the default source for new fields is `property`. |
| 74 | +This guarantees that the specified property exists. |
| 75 | +Also in case of the source has to be `value`, the configuration tool forces to switch the `source` attribute. |
| 76 | +==== |
| 77 | +|=== |
| 78 | + |
3 | 79 | == Version 0.11.2
|
4 | 80 | [cols="1,2,<10a", options="header"]
|
5 | 81 | |===
|
|
0 commit comments