apigee tool deploy to different env

[babuk0930]

Does apigeetool deploys to higher environment from the same code base and replace the targetendpoint/targetservers from some kind of properties file similar to maven plugin

In mavenplugin we have config.json and edge.json for higher env properties and maven will build new configuration zip file based on those properties and imports to apigee edge.

Ex: https://github.com/apigee/apigee-config-maven-plugin/tree/master/samples/APIandConfig/HelloWorld

Do we have similar functionality in apigeetool too? If so how to do it

[kurtkanaskie]

Yes, please see the docs here:

https://github.com/apigee/apigeetool-node#createTargetServer

For example:

$ apigeetool createTargetServer -N -o amer-demo13 -e test --targetServerName test-target --targetHost httpbin.org --targetPort 443 --targetSSL true | jq
{
  "host": "httpbin.org",
  "isEnabled": true,
  "name": "test-target",
  "port": 443,
  "sSLInfo": {
    "ciphers": [],
    "clientAuthEnabled": "false",
    "enabled": "true",
    "ignoreValidationErrors": false,
    "protocols": []
  }
}