Ability to customize Target Endpoint XML for deployment

[doublerebel]

Right now, Target Endpoint XML is overwritten with minimal settings (deploynodeapp.py#L128) on every deploy.

I would like to add environment variables to the ScriptTarget node, as described in the docs (Add a node.js application...). But currently I must set these by hand in the admin panel after deployment.

Ideally, the deploy script would read the variables out of a .env file, the system supported by Heroku/Foreman and node-foreman/Upstart. I use node-foreman for local development of my node.js apps before deploying to Heroku, Ubuntu VPS, or Apigee.

However, it would be reasonably easy to create the TargetEndpoint XML from my existing .env file as a build step, if I could define my own TargetEndpoint XML for deployment.

[gbrail]

This is a good idea.

We're working on a new version of apigeetool, built in Node.js, that contains a bunch of enhancements. What would you think about doing this in that tool? (Also, it'd be cool if you could try it out...)

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

or

npm install apigeetool

(note that the binary is still called "apigeetool" so if you "npm install -g apigeetool" it will overwrite the current Python tool that you have installed.)