apigee / apigee/apigeetool-node
apigeetool when deploying a proxy doesn't support setting the virtualhosts as in deploying a nodeapp
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 91
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
We have our own instance of Apigee and when trying to deploy a node app we do the following:
apigeetool deploynodeapp -u sdoe@apigee.com -o sdoe -e test -n 'Test Node App 2' -d . -m app.js -b /node2 -v 'default,secure'
But this same option is not available when deploying a proxy:
apigeetool deployproxy -u sdoe@example.com -o sdoe -e test -n example-proxy -d .
you can't do this:
apigeetool deployproxy -u sdoe@example.com -o sdoe -e test -n example-proxy -d . -v 'default,secure'
Any ideas how to overcome this without defining it into the XML code?
Thanks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the deployproxy and deploynodeapp command entry points and how each handles the -v virtualhosts option. Done means deployproxy accepts the documented option and passes the selected virtualhosts through during deployment without requiring XML changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100