v0.10.0

Changes

#30: New property "source" for fields and certificates to specify the source for the values or passwords.

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,
      "type": "string", 
      "used": true, 
      "value": null
    }
  }

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",
    "type": "string",
    "used": true,
    "value": "property.name"
  },
  "field#1": {
    "source": "value",
    "type": "string",
    "used": true,
    "value": "field value"
  }
}

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",
  "type": "p12"
}
...
"update": {
  "file": "cert/server.p12",
  "password-property": "property.name",
  "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",
  "source": "password",
  "type": "p12"
}
...
"update": {
  "file": "cert/server.p12",
  "password": "property.name",
  "source": "property",
  "type": "p12"
}

Features

#29: Add support for environment variables for field and password configuration.

The source property new supports a new value env to specify an environment variable as the source for field values and certificate passwords.

Environmentalized Fields

  "field#0": {
    "source": "env",
    "type": "string",
    "used": true,
    "value": "ENV_NAME"
  }

Certificates

"update": {
  "file": "cert/server.p12",
  "password": "SERVER_PASSWORD",
  "source": "env",
  "type": "p12"
}

v0.9.2

Bugs

#28: "process hasn't exited" error on executing external commands

The "process hasn't exited" error on executing external commands is fixed.

v0.9.1

Bugs

#27: Prevent entity store update in simulation mode

The buildfed shall not update the in-memory entity store in simulation mode.

Features

#26: MinGW Support

Add MinGW (Minimalistic GNU for Windows) support for buildfed.sh.

Remark: MinGW is provided as part of Git for Windows. This enhancement allows to execute the plugin within a Git Bash shell on Windows.

v0.9.0

Bugs

• #22: Passpharse bug fixed on using API Gateway 7.6.2

Changes

• #24: Logging used for Python scripts instead of 'print'.

Features

#23: Multiple Property Files

Additionally to the axway.config.props property, property files can be configured via the element of the element or via the axway.config.props.files property.

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>
      <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:

1. File specified by axway.config.props property.
2. Files specified in the element.
3. Files specified by axway.config.props.files property.

If a property exists in multiple property files the value of from the last property file is used.

v0.8.1

Bugs

• #20: configuration tool now supports API Gateway 7.5.3
• #21: support verbose mode of configuration tool for goal apigw:deploy

v0.8.0

Changes

Replaced Properties

Following properties are no longer supported:

• axway.passphrase.in: replaced by axway.passphrase.pol
• axway.passphrase.out: replaced by axway.passphrase.out
• propertyFile: replaced by axway.config.props
• certsFile: replaced by axway.config.certs

Features

#11 New goal apigw:deploy

The plugin now supports to deploy a project directly via the plugin goal apigw:deploy. Only the standard deployment is supported. The deployment of static files and JARs is not supported.

New properties:

• axway.anm.host: Host of the Admin Node Manager.
• axway.anm.port: Port of the Admin Node Manager (default: 8090).
• axway.anm.user: User to connect to the Admin Node Manager (default: admin).
• axway.anm.password: Password of the user.
• axway.deploy.group: Name of the group the project is deployed to.
• axway.passphrase.pol: Passphrase for .pol and .env packages.
• axway.passphrase.fed: Passphrase for .fed packages.
• axway.passphrase.deploy: Passphrase for deployment group.
• axway.config.envs: Path to environmentalized fields configuration file.
• axway.config.certs: Path to certificates configuration file.
• axway.config.props: Path to properties configuration file.