| ID | Type | Description |
|---|---|---|
Bug Fix |
Update versions of dependencies. |
| ID | Type | Description | ||
|---|---|---|---|---|
Enhancement |
Add support for multiple base directories for certificates. |
|||
Enhancement |
Read properties from stdin. If the filename of the Example of flat key/value JSON
{
"prop1": "value1",
"prop2": "value2"
}
|
| ID | Type | Description |
|---|---|---|
Enhancement |
The property configuration now supports JSON boolean values. {
"properties": {
"enables": false (1)
}
}
|
|
Bug |
In case the entity field configuration file doesn’t exist the following error occurs:
This is fixed. If the configuration file doesn’t exists the file will be created automatically. |
|
Enhancement |
Customized version name for A new property Example Command line
pom.xml
<properties>
<axway.project.version>${project.version}-BN20201031</axway.project.version>
</properties> |
|
Enhancement |
Docker capabilities. |
| ID | Type | Description |
|---|---|---|
Enhancement |
Improve error message in case of wrong certificate passphrase. |
|
Bug |
Base path for certificates is ignored by If the |
| ID | Type | Description |
|---|---|---|
Enhancement |
Base directory for certificate files. Use the |
|
Enhancement |
Support for confidential properties. For confidential properties the configuration tools supports to pass a secrets file. It is a JSON file where the values of the properties are encrypted by a key. |
| ID | Type | Description | ||
|---|---|---|---|---|
Enhancement |
Support removal of certificates. A new certificate type {
"certifictates": {
"to-be-deleted": {
"origin": {
"info": {
"not_after": "2020-08-23T20:24:00+02:00",
"subject": "CN=localhost, O=ACME Inc., C=EX"
}
},
"update": {
"type": "empty" (1)
}
}
}
|
|||
Enhancement |
The default source for new environmentalized fields is Old default source
{
"field#0": {
"source": "value", (1)
"type": "string",
"used": true,
"value": null
}
}
New default source
{
"field#0": {
"source": "property", (1)
"type": "string",
"used": true,
"value": null
}
}
|
| ID | Type | Description |
|---|---|---|
Bug |
For configuration files in the old format having fields with "property" attribute set to null, the field will not be upgraded to the newer version. Example
"fields": {
"attributeValue#0": {
"property": null,
"type": "string",
"used": true,
"value": "artifact"
}
}This results in the error message:
The bug is fixed and the configuration files will be upgraded to the new version, now. |
| ID | Type | Description |
|---|---|---|
Bug |
The configuration files are only updated if they are changed. Also a bug is fixed where the configuration will not be updated even if the |
| ID | Type | Description |
|---|---|---|
Enhancement |
The A new Example: $ buildfed ... -F description:config/description.txt This will define a new property |
|
Enhancement |
Build artifact information JSON. For server and deployment archives the plugin will generate a On configuring the |
| ID | Type | Description | ||
|---|---|---|---|---|
Enhancement |
New property "source" for fields and certificates to specify the source for the values or passwords. The are following advantages:
Environmentalized Fields For field values there are separate properties ("property" and "value") to configure the field value (see example below). Old Format
{
"field#0": {
"property": null, (1)
"type": "string",
"used": true,
"value": null (2)
}
}
A new property "source" is introduced to specify the source of the field value. The property defines the kind of the "value" property. In case of "source" is equal to "value" the field value is directly configured by the value of the "value" property. In case of "source" is equal to "property" the field value is retrieved from the property named by the "value" property. New Format
{
"field#0": {
"source": "property", (1)
"type": "string",
"used": true,
"value": "property.name" (2)
},
"field#1": {
"source": "value", (3)
"type": "string",
"used": true,
"value": "field value" (4)
}
}
Certificates For certificate passwords there are separate properties ("password" and "password-property") to configure the password (see example below). Old Format
"update": {
"file": "cert/server.p12",
"password": "server.password", (1)
"type": "p12"
}
...
"update": {
"file": "cert/server.p12",
"password-property": "property.name", (2)
"type": "p12"
}
A new property "source" is introduced to specify the source of the certificate password. The property defines the kind of the "password" property. In case of "source" is equal to "password" the password is directly configured by the value of the "password" property. In case of "source" is equal to "property" the password is retrieved form the property named by the "password" property. New Format
"update": {
"file": "cert/server.p12",
"password": "server.password", (1)
"source": "password", (2)
"type": "p12"
}
...
"update": {
"file": "cert/server.p12",
"password": "property.name", (3)
"source": "property", (4)
"type": "p12"
}
|
|||
Enhancement |
Add support for environment variables for field and password configuration. The Environmentalized Fields "field#0": {
"source": "env", (1)
"type": "string",
"used": true,
"value": "ENV_NAME" (2)
}
Certificates "update": {
"file": "cert/server.p12",
"password": "SERVER_PASSWORD", (1)
"source": "env", (2)
"type": "p12"
}
|
| ID | Type | Description |
|---|---|---|
Bug |
The "process hasn’t exited" error on executing external commands is fixed. |
| ID | Type | Description |
|---|---|---|
Enhancement |
Add MinGW (Minimalistic GNU for Windows) support for Remark: MinGW is provided as part of Git for Windows. This enhancement allows to execute the plugin within a Git Bash shell on Windows. |
|
Bug |
The |
| ID | Type | Description |
|---|---|---|
Fix |
Broken passphrase feature for API Gateway 7.6.2 is fixed. |
|
Enhancement |
Support for multiple property files. Additionally to the pom.xml
<plugin>
<groupId>com.axway.maven.plugins</groupId>
<artifactId>apigw-maven-plugin</artifactId>
<version>${axway.maven.plugin.ver}</version>
<extensions>true</extensions>
<configuration>
<configPropertyFiles> <!--(1)-->
<configPropertyFile>${basedir}/a.json</configPropertyFile>
<configPropertyFile>${basedir}/b.json</configPropertyFile>
</configPropertyFiles>
</configuration>
</plugin>
command line
$ mvn package -Daxway.config.props.files=c.json,d.json The files are used in the following order:
If a property exists in the multiple property files the value of from the last property file is used. |
|
Enhancement |
Use Python logging for |
| ID | Type | Description |
|---|---|---|
Enhancement |
Deployment to gateway via plugin. The plugin now supports to deploy a project directly via the plugin goal New properties:
Deleted properties:
|
| ID | Type | Description | ||
|---|---|---|---|---|
Enhancement |
Check expiration of configured certificates. The plugin and the configuration tool now supports to check if configured certificates expires within a given number of days. If at least one certificate expires within the time frame an error will be raised. For the configuration tool the check is disabled by default. For the plugin the default number of days is 10.
To disable the check for the plugin specify set |
|||
Enhancement |
Don’t create "info" section for "update" certificates. Information about the configured certificates are written to log instead. Previously the configuration tool has written the "info" section (see below). This will change a source file, which is not suitable for build environments. previous-cert-config.json
"update": {
"file": "cert/server.p12",
"info": { (1)
"not_after": "2020-05-21T07:02:00+02:00",
"subject": "CN=server, O=Axway, L=Berlin, ST=Berlin, C=DE"
},
"password": "server",
"type": "p12"
}
The "info" section is no longer created or updated for "update" certificates. cert-config.json
"update": {
"file": "cert/server.p12",
"password": "server",
"type": "p12"
}
|
|||
Fix |
On flattening the resulting POM a NullPointerException occurred if the The issue occurred for server and deployment projects. |
| ID | Type | Description | ||
|---|---|---|---|---|
Enhancement |
Optionally skip For CI/CD pipelines it would be usefully to separate the package and deployment phase.
A property
|
|||
Enhancement |
Support simulation mode for configuration tool. In simulation mode no output files ( To ensure proper configuration files, unconfigured fields or certificates will still raise a build error.
|
| ID | Type | Description |
|---|---|---|
Enhancement |
Configuration tool now supports passphrases for input archives (.pol and .env) and for output archives (.fed and .env). Example: buildfed -e gateway.env -p gateway.pol -c gateway.config.json -passphrase-in=foo -passphrase-out=bar --output-fed=gateway.fed Uses the passphrase "foo" to open the Limitation:
|
|
Enhancement |
The source directory layout for the configuration tool is changed. The tool can be invoked directly from the cloned project folder, now. Example: Windows > git clone https://github.com/Axway-API-Management-Plus/apigw-maven-plugin.git > cd apigw-mavem-plugin > set AXWAY_HOME=c:\axway > src\main\resources\scripts\buildfed.cmd -h Unix $ git clone https://github.com/Axway-API-Management-Plus/apigw-maven-plugin.git $ cd apigw-mavem-plugin $ export AXWAY_HOME=/opt/axway $ src/main/resources/scripts/buildfed.sh -h Extracting the tool from the Maven plugin via the |
|
Fix |
Configured certificates were not updated by configuration tool. Now updating or adding certificates works as expected. |
|
Enhancement |
Example for using standalone configuration tool added. Folder: |
|
Enhancement |
Working directories of PolicyStudio consolidated under a single |
|
Enhancement |
Generate default |
|
Enhancement |
Maven plugin now supports passphrases for reading input packages and for writing output packages. Applicable for server and deployment packages only. You can use the properties Examples: ~/server-project$ mvn -Daxway.passphrase.out=changeme clean install Generates a server archive containing passphrase protected ~/deploy-project$ mvn -Daxway.passphrase.in=changeme -Daxway.passphrase.out=changed clean install Uses a passphrase protected server archive and generates a deployment archive containing a passphrase protected |