Releases: apigee/apigee-config-maven-plugin
v1.3.1
v1.2.2
v1.2.1
Feature release:
Support for CPS KVM.
Bugs fixed:
Fix Issue 30
Fix Issue 29
Description:
CPS enabled orgs introduce a newer management API to update KVM entries. This release provides support for CPS enabled orgs as well as non-CPS orgs. No user visible changes to configuration or command line options introduced.
v1.2
Export Dev App Keys
Export the dev apps details to a json file (devAppKeys.json). With the exported info, you can tie it with your CI/CD process and trigger the automated test cases that requires the dev app credentials.
To export, the command is
mvn apigee-config:exportAppKeys -P{profileId} -Dapigee.config.exportDir=./someDir
The export command is exposed as a separate goal - exportAppKeys
v1.1.3
Feature release supporting broken down config file structure typically found as resources/edge/.../*.json
Refer to samples. A new flag apigee.config.dir is added to pick the directory containing the config files.
Support for maskconfigs (data masks) is also added.
http://docs.apigee.com/api-services/content/data-masking
v1.1.2
v1.1.1
Feature release adding support for "delete" and "sync" options.
To delete config listed in edge.json. Useful to clean Edge so that a subsequent "create" can setup config in a clean environment.
apigee.config.options=delete
Performs a Delete and then a Create.
apigee.config.options=sync
Added individual goals to Readme. This plugin can pick a specific config type like keyvaluemaps and apply the action (create, update or delete) only on the keyvaluemaps specified in edge.json. This provides a lot of flexibility in CI tooling as well as dev, QA or migration scenarios.
v1.1
Feature release that adds support for KVM (org, env, API scopes).
Does not support KVM CPS version yet.